Roadmap
Milestone: 0.12.8
22 months late (Sep 2, 2015, 3:00:00 AM)
87%
Total number of tickets: 8 - closed: 7 - in progress: 0 - new: 1
Next maintenance release for 0.12-stable (LTS)
Note to maintainers:
- Move tickets here if they need to be fixed for the 0.12.8 release.
- There should be no enhancements here, only major defects here anyway, focus is now on the 1.x versions (next-stable-1.0.x, next-stable-1.2.x and next-dev-1.3.x)
Top translations: trac » 0_12-stable-messages-js-pot
Codeline: branches/0.12-stable
Milestone: 1.3.2
6 months late (Dec 15, 2016, 12:00:00 AM)
94%
Total number of tickets: 56 - closed: 53 - in progress: 2 - new: 1
Next development release for 1.3.x
Python 2.7 is now mandatory. Jinja2 (2.9.3+) is now the template engine of choice, but Genshi is still supported.
See also corresponding drafts for API changes and release notes.
Note to maintainers:
- Move tickets from next-dev-1.3.x to here once you're sure you're going to fix them for the 1.3.2 release.
- There should be mostly enhancements tickets here, defects should first be fixed on next-stable-1.2.x if possible
demo-1.3 is running a recent version of trunk / 1.3.2dev
Codeline: trunk
Milestone: 1.2.2
10 days late (Jun 3, 2017, 9:00:00 AM)
89%
Total number of tickets: 18 - closed: 16 - in progress: 2 - new: 0
Next maintenance release for 1.2-stable
Note to maintainers:
- Move tickets from next-stable-1.2.x to here once you're sure you're going to fix them for the 1.2.1 release.
- There can be minor enhancements here, but nevertheless we should dedicate this branch to fixing defects still present in 1.2
Top translations: trac » 1.2-stable-messages-js-pot
Top translations: trac » 1.2-stable-tracini-pot
Codeline: branches/1.2-stable
Milestone: 1.2.3
Due in 3 weeks (Jul 2, 2017, 3:00:00 AM)
0%
Total number of tickets: 7 - closed: 0 - in progress: 5 - new: 2
Milestone: 1.3.3
Due in 5 weeks (Jul 16, 2017, 3:00:00 AM)
0%
Total number of tickets: 8 - closed: 0 - in progress: 5 - new: 3
Milestone: 1.4
Due in 7 weeks (Aug 2, 2017, 3:00:00 AM)
Next major release
Note to maintainers:
- Move tickets from next-stable-1.4.x to here once you're sure you're going to fix them for the 1.2 release.
Top translations: trac » trunk-messages-js-pot
Top translations: trac » trunk-tracini-pot
Codeline: trunk
Milestone: 1.0.15
Due in 3 months (Sep 3, 2017, 3:00:00 AM)
25%
Total number of tickets: 4 - closed: 1 - in progress: 1 - new: 2
Next maintenance release for 1.0-stable
Note to maintainers:
- Move tickets from next-stable-1.0.x to here once you're sure you're going to fix them for the 1.0.15 release.
- There can be minor enhancements here, but nevertheless we should dedicate this branch to fixing defects still present in 1.0
Top translations: trac » 1.0-stable-messages-js-pot
Top translations: trac » 1.0-stable-tracini-pot
Codeline: branches/1.0-stable
Milestone: 1.5.1
Due in 7 months (Jan 1, 2018, 3:00:00 AM)
0%
Total number of tickets: 2 - closed: 0 - in progress: 0 - new: 2
Milestone: next-dev-1.3.x
No date set
0%
Total number of tickets: 76 - closed: 0 - in progress: 14 - new: 62
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.2.x).
Eventually some of the topic milestones will be part of this release as well:
Note to maintainers:
- Move to 1.3.2 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.2.x if possible
Codeline: trunk
Milestone: next-major-releases
No date set
0%
Total number of tickets: 483 - closed: 0 - in progress: 2 - new: 481
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
Milestone: next-stable-1.0.x
No date set
0%
Total number of tickets: 2 - closed: 0 - in progress: 0 - new: 2
Next maintenance release series for 1.0-stable
Pool of tickets which are going to be implemented in one of the next minor releases for the stable branch of Trac (1.0.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.3.x
- Move stuff to the current maintenance release (1.0.14) once you're sure you're going to implement it for that release
Codeline: branches/1.0-stable
Milestone: next-stable-1.2.x
No date set
0%
Total number of tickets: 148 - closed: 0 - in progress: 8 - new: 140
Next maintenance release series for 1.2-stable
Pool of tickets which are going to be implemented in one of the next minor releases for the stable branch of Trac (1.2.x).
Note to maintainers:
- There should be no major enhancements here, only defects and minor enhancements; major new features will go to next-stable-1.2.x
- Move stuff to the current maintenance release (1.2.1) once you're sure you're going to implement it for that release
Codeline: branches/1.0-stable
Milestone: not applicable
No date set
78%
Total number of tickets: 99 - closed: 77 - in progress: 3 - new: 19
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
wontfixis 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
projectcomponent)
Tickets that concern Trac but are not part of the schedule are assigned to unscheduled.
Milestone: plugin - mercurial
No date set
71%
Total number of tickets: 48 - closed: 34 - in progress: 3 - new: 11
Overview of tickets applicable to the TracMercurial plugin:
- #8417
- CachedRepository support in TracMercurial
- #10515
- LookupError, <file> not found in manifest
- #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
- #10552
- TracMercurial hooks.py dies when using TortoiseHg
- #10719
- Abort: cannot follow file not in parent revision: "tracext/hg/backend.py"
- #10950
- [hg] encoding setting is not used for files in hg
- #11044
- Include Mercurial support in Trac distribution
- #12160
- mercurial-plugin should have unit tests
- #12176
- MercurialConnector should log the import errors
- #12177
- Quickjump should list all bookmarks, not only those of current revision
Codelines: [email protected], [email protected]
Milestone: plugin - spam-filter
No date set
97%
Total number of tickets: 79 - closed: 77 - in progress: 0 - new: 2
Overview of tickets applicable to the SpamFilter plugin.
Codeline: plugins/1.0/spam-filter
Milestone: topic-multiproject
No date set
0%
Total number of tickets: 4 - closed: 0 - in progress: 0 - new: 4
Topic milestone, all tickets corresponding to support for MultiProject.
Milestone: topic-wikiengine
No date set
0%
Total number of tickets: 26 - closed: 0 - in progress: 0 - new: 26
Topic milestone, all tickets corresponding to the new WikiEngine.
Milestone: translations
No date set
3%
Total number of tickets: 37 - closed: 1 - in progress: 6 - new: 30
Tickets for coordinating the translation effort, see TracL10N.
Milestone: undecided
No date set
0%
Total number of tickets: 27 - closed: 0 - in progress: 0 - new: 27
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.
Milestone: unscheduled
No date set
0%
Total number of tickets: 209 - closed: 1 - in progress: 0 - new: 208
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".
