[[PageOutline]]
= TracDev ToDo List =

== Release [milestone:0.12.1] ==

 - see what remains to be done, move the rest to [milestone:0.12.2] (getting nearer...)
 - prepare release ticket, propose a schedule (string freeze, rc1, test freeze, final), mail trac-dev

== [milestone:0.13] ==

Development process enhancements:
 - DVCS mirrors for Git and Mercurial (#9235 - improve docs)
   - improve log module (#1492 and #3236)
 - reorganization of milestones, [milestone:next-major-0.1X] becoming the main pool of targeted tickets



Bug fixing and performance improvements.
 - #6348, soon to earn the ''most postponed bugfix'' prize ;-)
 - #8507 improve explicit gc

Tools:
 - Python 2.5 - `with env.transaction as db`, `with env.read_db as db` - #9536, soon (TracDev/DatabaseApi#Trac0.13API)


Main features:
 - #31 and #886 (experimental repos:ticket-links)
 - #4431 and related wiki improvements (experimental branch http://github.com/cboos/trac/tree/wikiparser)
 - TracDev/Proposals/MultipleProject
 - #2456 - users, #5648 - groups

Minor features:
  * i18n
    - #2182 - test jun's branch 
    - perhaps translation for workflow status and action names (#5441) 
    - early loading and caching of catalogs (was discussed in #9439)
  - __More revisions available__ link at the bottom of revision log, when viewing a partial revision set  (#4854 actually)

== For later - [milestone:next-major-0.1X] ==

 - Help delegator  (ticket:2656#comment:26)
 - Custom Queries: #7026 - redo with jQuery UI drag'n'drop?
 - Version Control:
   - `CachedRepository.get_path_history` 
 - Template: replace support for Clearsilver with support for Jinja2 - TracDev/Proposals/Jinja //(less urgent now that we have a good Genshi 0.6 release)//

== Mercurial plugin ==
 -  #1492 - `log --follow-first` (check, isn't that already done?)
 - add basic support for cached repo (#8417)
 - show merge changesets in revision log (#3236)

== Git plugin ==
 - #1492 - `log --first-parent` support

== Miscellaneous

 * **sort order of tickets in search results**: I expected this to be based on the most recent modification time first? It's seems it's creation time first...

 * Verify this one, not sure yet it's a bug which is still present or a transient error that happened in between updates:
{{{
2010-02-26 19:24:14,087 Trac[changeset] WARNING: Diff rendering failed for property svn:mergeinfo with renderer SubversionMergePropertyDiffRenderer:
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/trac/versioncontrol/web_ui/changeset.py", line 798, in render_property_diff
    options)
  File "build/bdist.linux-x86_64/egg/trac/versioncontrol/svn_prop.py", line 297, in render_property_diff
    all_revs = set(repos._get_node_revs(spath))
  File "build/bdist.linux-x86_64/egg/trac/versioncontrol/cache.py", line 290, in _get_node_revs
    slast = '%010d' % last
TypeError: int argument required
}}}

 * In TracInstall#GeneratingtheTraccgi-bindirectory, there's the mention of ''chicken/egg'' problem with `trac-admin deploy`. I've been bitten by this as well and I think we should support a direct `trac-admin deploy <target>` call syntax, i.e. without the need to specify a (dummy) environment.




----
''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.''