Roadmap

Next stable version for the 1.6.x release line

Note to maintainers:

• Move tickets from next-stable-1.6.x to here once you're sure you're going to fix them for the 1.6.1 release.
• There can be minor enhancements here, but nevertheless we should dedicate this branch to fixing defects still present in 1.6

_{demo-1.6 is running 1.6}

Codeline: branches/1.4-stable

Next development release series

Pool of tickets which are going to be implemented in one of the next minor releases for the development branch of Trac (1.5.x).

Eventually some of the topic milestones will be part of this release as well:

• topic-wikiengine
• topic-multiproject
• see also TracDev/ReleaseNotes/1.8

Note to maintainers:

• Move to 1.5.1 once you're sure it can be finished for that release
• There should be mostly enhancements tickets here, defects should first be fixed on next-stable-1.4.x if possible

Codeline: trunk

Pool of tickets which are going to be implemented in one of the next major releases.

The tickets in 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

Codeline: trunk

Next maintenance release series for 1.6-stable

Pool of tickets which are going to be implemented in one of the next minor releases for the stable branch of Trac (1.6.x).

Note to maintainers:

• There should be no major enhancements here, only defects and minor enhancements; major new features will go to next-dev-1.7.x
• Move stuff to the current maintenance release once you're sure you're going to implement it for that release

Codeline: branches/1.6-stable​

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 3^rd 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:

Codelines: mercurial-plugin@1.0, mercurial-plugin@0.13, mercurial-plugin@0.12

Overview of tickets applicable to the SpamFilter plugin.

Codeline: plugins/1.0/spam-filter​

Topic milestone, all tickets corresponding to support for MultiProject.

Topic milestone, all tickets corresponding to the new WikiEngine.

Tickets for coordinating the translation effort, see TracL10N.

This milestone collects the tickets which need a deeper look in order to be triaged.

Usually moved there from {20} when they resist a quick triaging attempt.

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