Roadmap
Next major release for trunk
Installation Prerequisites
Python 2.5, 2.6 or 2.7 is needed, as support for Python 2.4 has been dropped.
Otherwise, the requirements are the same as those for 0.12:
- Genshi's 0.6 is required
- Babel 0.9.5 is needed and needs to be installed first if you want to enjoy localization support
Highlights of this release
See the TracDev/ReleaseNotes/0.13. The 0.13/TracGuide contains the updated user and administrator documentation. Trac 0.13 will also be the first release to feature complete TracDev/ApiDocs! Plugin writers will also find a detailed list of the API changes in TracDev/ApiChanges/0.13.
This release requires an environment upgrade.
Note to maintainers:
- Move tickets from next-major-0.1X to here once you know you're going to implement them for the 0.13 release.
- We should try to stay below 100 tickets, so maybe consider moving back a ticket to next-major when adding a new one…
This Trac instance is using Trac 0.13dev-r11029, Genshi 0.6 and Babel 0.9.5 Codeline: trunk
Next minor release for 0.12-stable
Note to maintainers:
- Move tickets from next-minor-0.12.x to here once you're sure you're going to fix them for the 0.12.4 release.
- There should be no enhancements here, only defects
- There should be only major defects here anyway, focus is now on 0.13
Next feature release, in planning stage.
Eventually some of the topic milestones will be part of this release as well:
Note to maintainers:
- move here the tickets you want to work on next but you know are not going to make it for 0.13
Topic milestone, all tickets corresponding to support for MultiProject.
Topic milestone, all tickets corresponding to the new WikiEngine.
Pool of tickets which are going to be implemented in one of the next major releases.
The tickets on this milestone have the endorsement of the Trac developers.
- their priority is a rough indicator of the schedule, from highest (soon) to lowest (long term goal)
- their severity is an indicator of the impact of the ticket on Trac
Note to maintainers:
- Valid tickets which might fit in Trac core but are not fulfilling the criteria above go into unscheduled
Pool of tickets which are going to be implemented in the next minor releases (0.12.x).
Note to maintainers:
- There should be no enhancements here, only defects
The not applicable milestone is a special milestone which is currently used to distinguish between tickets that have not yet been triaged (see TracTicketTriage) and those who have, but for which there's no "real" milestone deemed to be adequate.
This can happen in the following situations:
- for bugs concerning a 3rd party software (like Subversion), which are occurring frequently enough to be kept opened and documented here, until an external resolution is found (when closing such tickets as wontfix is not really an option, as this would discourage people for following the progress, reporting the workarounds, etc.)
- for tasks to be done on t.e.o (usually in association with the project component)
Tickets that concern Trac but are not part of the schedule are assigned to unscheduled.
Overview of tickets applicable to the TracMercurial plugin:
- #8417
- CachedRepository support in TracMercurial
- #10247
- TracMercurial dies with Mercurial 1.9
- #8068
- Mercurial bundle attachments should be viewable in readable representation.
- #9704
- Support for subrepositories mercurial extension
- #9852
- Mercurial plugin support for pulling repository description from hgrc
- #10136
- Way to configure by default displayed branch
- #10411
- Enhancing TracMercurial plugin to use new server-command protocol
- #10477
- Post-commit hook gives strange answer
- #10527
- Mercurial bookmarks as properties in browser
- #10552
- TracMercurial hooks.py dies when using TortoiseHg
Overview of tickets applicable to the SpamFilter and SpamFilter/Captcha plugins.
Tickets for coordinating the translation effort, see TracL10N.
All tickets that are neither invalid nor rejected, but simply not part of the road map defined by the Trac developers.
If a ticket ends up here, it means it probably will never get done unless someone steps up to champion it, becomes an active member of the Trac team and implements it. See also "PatchWelcome".
