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:
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:
This Trac instance is using Trac 0.13dev-r10932, Genshi 0.6 and Babel 0.9.5 Codeline: trunk
Next minor release for 0.12-stable
Note to maintainers:
Next feature release, in planning stage.
Eventually some of the topic milestones will be part of this release as well:
Note to maintainers:
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.
Note to maintainers:
Pool of tickets which are going to be implemented in the next minor releases (0.12.x).
Note to maintainers:
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:
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".
