Roadmap
Bug fix and maintenance release.
Tickets coming from 0.12 which are not essential for the 0.12 release itself but are nevertheless deemed high priority for the maintenance cycle.
Note to maintainers:
- Move tickets from next-minor-0.12.x to here once you know you're going to fix them for the 0.12.1 release.
- There should be no enhancements here, only defects
Next major release, currently in planning stage.
See TracDev/ReleaseNotes/0.13 for the major features.
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.
Last bug fix release for 0.11.x.
Pool of tickets which are going to be implemented in the next major releases.
The tickets on this milestone have the endorsement of the Trac developers.
- the priority is a rough indicator of the schedule, from highest (soon) to lowest (long term goal)
- the severity is an indicator of the impact of the ticket on Trac
Note to maintainers:
- Tickets 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.
- #7160
- Problems with character encoding
- #7217
- Non-ASCII characters get replaced with '?' in changeset metadata
- #8180
- Bad encoding in mercurial plugin
- #8417
- CachedRepository support in TracMercurial
- #8538
- support non-ascii filenames in mercurial vcs backend
- #9161
- Unsupported version control system "hg" "cannot import name cachefunc"
- #8068
- Mercurial bundle attachments should be viewable in readable representation.
- #8628
- Considering revision 0 as oldest revision in TracMercurial.
- #8697
- hg commit comments with text 'rDDD' where 'D' is a digit cause UnicodeDecodeError
- #8927
- UnicodeDecodeError for non-existing changesets in marked up text
- #9009
- Mercurial plugin doesn't support multirepos wiki syntax
Overview of tickets applicable to the SpamFilter and SpamFilter/Captcha plugins.
Tickets for coordinating the translation effort, see TracL10N.
Temporary milestone, grouping tickets formerly on milestone 1.0 and 2.0.
Tickets here will be re-triaged, mainly between next-major-0.1X and unscheduled.
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".
