Version 65 (modified by 14 years ago) ( diff ) | ,
---|
TracDev ToDo List
Ticket Triage
In preparation for 0.12:
- move some more 0.12 tickets to next-minor-0.12.x, keep on 0.12 proper only what can realistically go in 0.12
- move enhancements tickets of next-minor-0.12.x tickets to later next-major-0.1X, 1.0
Release 0.11.7?
Seems that we might need it…
I've just noticed a disturbing issue with 0.11.6:
when creating a new milestone through the admin panel,
the other trac.fcgi processes didn't pick up the new value,
so either we don't do a config.touch()
in this case,
or there's a race.
Well, we do
TicketSystem(self.env).reset_ticket_fields()
in source:tags/trac-0.11.6/trac/ticket/model.py@#L702, so it looks like we have a race…
Release 0.12
- database
- #6348 and a few others
- ticket query system:
- #7026 — 0.13?
- i18n:
- multirepos: see 0.12-multirepos
- #8731
- #5640 and #7116
- merge
- ideally, document the whole thing first, i.e. 0.12/TracRepositoryAdmin
- Version Control:
CachedRepository.get_path_history
- WikiRename: clean-up, sync, reintegrate
For Later (0.13, …, 1.0)
- Version Control:
- merge type #1492
- #2456 - not too early to start thinking about it seriously
- start experimenting with TracDev/Proposals/MultipleProject
- remove support for pysqlite 1.1.x in source:trunk/db/sqlite_backend.py
Mercurial plugin
- add basic support for cached repo
log --follow-first
- show merge changesets in revision log (#1492)
To editors: this is not the place where to put your favorite ticket (see SeaChange/WhatUsersWant instead); this page must be kept short and is mainly for improving the clarity of the ongoing development activity in the TracTeam.