[[PageOutline]]
= TracDev ToDo List =

== Ticket Triage ==

In preparation for 0.12:
    - move some more 0.12 tickets to [milestone: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 
      [milestone:0.13], [milestone:1.0], but first:
      - move current 0.12.1 tickets to [milestone:0.12-stable]
      - move some of the current 0.13 tickets to [milestone:next-major]



== Release [milestone: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 [milestone:0.12] ==
 - database
    - #6348 and a few others 
 - ticket query system: 
   - #7026 -- 0.13?
 - i18n:
   - translation of javascript (#6353, Babel:#110) -- 0.12-stable?
   - translation of workflow (#6234) -- 0.12-stable or 0.13?
   - ~~get rid of `plural` in macros.html and use proper i18n API for this~~ -- done in [8666]
 - multirepos: see [milestone: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 ([milestone:0.13], ..., [milestone: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.''