Roadmap
-
Bug fixes and minor improvements.
The release candidate 0.11.5rc1 is out - please test!
-
Main features considered for this release:
- i18n and localizations
Note that you'll need Genshi's genshi:source:branches/experimental/advanced-i18n (using trunk mostly works but fails tests, using 0.5.1 will not work at all). - Better help/documentation system (#2656) - TracDev/Proposals/NewHelp
- Improved ticket query system (so that it can be used instead of SQL reports system in 99% of the use cases)
See 0.12 for the updated parts of the Trac guide, which describes most of the new features.
Note: This release requires a database upgrade since [8071] (trac-admin $TRAC_ENV upgrade).
In the works:
- MultipleRepositorySupport
- newhelp branch
Experimental:
- TracSqlAlchemy: experiment with SQLAlchemy for database interfacing and connection pooling (see sandbox/sqlalchemy-ng)
Revision Log
- log:trunk@6942:head more details.
- see TracDev/ReleaseNotes/0.12 for a summary of the user visible changes
- see TracDev/ApiChanges/0.12 for a summary of the developer visible changes
- i18n and localizations
-
Bug fixes and minor improvements to 0.12.
This milestone also contains tickets corresponding to known issues from Trac 0.11.x which have now been moved to the 0.12.x series.
-
- Improved plugin installation (easier, more robust)
- Improved user/session system
- Pluggable user-directory provider (#2456)
- Improved "ticket monitoring"
- Optional form-based login
- Improved notification architecture
- Planned API changes:
- Improved user/group API
-
Code name Romero
- Support for multiple projects
- basic support for multiple projects
- project index and summary page (#1)
- common timeline, common search
- AdvancedSearch
- Improved API for request handlers (see sandbox/controller and the newer VcRefactoring/Controller experiment for inspiration)
- 'My Summary' (#150)
- Support for multiple projects
-
- Incorporate alien technology
-
The experimental milestone is a special milestone which is temporarily used for re-triaging tickets that were once assigned to some effective milestone, but for which the implementation plan has changed.
Those are mainly the tracobject, xref tickets for which the proposed design is only experimental and not part of Trac's official roadmap.
-
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 SpamFilter and TracMercurial plugins, which are not formally associated to a Trac release (WebAdmin plugin related issues are associated to 0.10.x milestones, as for 0.11, it's not a plugin anymore but a component of Trac core)
- 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)
OTOH, blue sky ideas are still to be targeted for 2.0.
