Version 59 (modified by 15 years ago) ( diff ) | ,
---|
TracDev ToDo List
Ticket Triage
- move some more 0.12 tickets to 0.12.1, keep on 0.12 proper only what can realistically go in 0.12
- move enhancements tickets of 0.12.1 tickets to later 0.13, 1.0
- create 0.12-multirepos milestone and assign multirepos tickets to it
Release 0.11.6
- #7490 - see TracPerformance. This is going to end up as a caveat paragraph in TracInstall…
Most ideas suggested in TracDev/Performance should be done for 0.12, tested there and eventually backported.
Same for remaining database tickets - at this point they should probably first go to trunk, then eventually be backported.
Release 0.12
- check and integrate important contributions:
- database
- #6348 and a few others
- remove support for pysqlite 1.0.x in source:trunk/trac/db/sqlite_backend.py (#8625)
- remove support for pyPgSql in source:trunk/trac/db/postgres_backend.py (#8539)
- ticket query system:
- i18n:
lazy activation of translations, so that we don't instantiate a session on every request (req.locale ⇒ req.session)- translation of javascript (#6353, Babel:#110)
- translation of workflow (#6234)
- get rid of
plural
in macros.html and use proper i18n API for this - fix the extraction of value attributes in templates (not sure anymore)
translate navigation links
- multirepos: see MultipleRepositorySupport#RelatedTickets
- Version Control:
- merge type #1492
CachedRepository.get_path_history
- WikiRename: clean-up, sync, reintegrate
For Later (0.13, …, 1.0)
- #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.
Note:
See TracWiki
for help on using the wiki.