Roadmap
-
Bug fixes and minor improvements.
If you're using the trac-post-commit-hook and a scoped repository then you need this version (see r5309).
See changes: log:branches/0.10-stable@5237:head
Last backports planned before branch freeze:
-
Feature Summary
Trac 0.11 features numerous bug fixes and improvements over 0.10:
- easier installation:
Trac is now much easier to install as we replaced the ClearSilver template engine by Genshi, a pure-Python template engine. The use of SetupTools also facilitates the installation of Trac and its dependencies.
See TracInstall. - support for fine-grained permission, allowing very flexible control over what an user can see or do in the whole system
- support for configurable workflow in the ticket subsystem
- support for Pygments as the default syntax highlighter
- improved repository browser ("blame" support, dynamic in-place expansion of folders)
- see TracDev/ReleaseNotes/0.11 for a summary of the user visible changes
- see TracDev/ApiChanges/0.11 for a summary of the developer visible changes
Development Status
- the rc1 is now released. Please help us making a great 0.11 release by testing it now!
- Revision Log
- log:trunk@3804:head more details.
Caveats
- Coming from 0.10.x, an environment upgrade is needed (trac-admin $TRAC_ENV upgrade) and you can't downgrade to 0.10-stable without some manual intervention, so keep a backup at hand ;-)
- easier installation:
-
Bug fixes and minor improvements.
See also TracDev/ToDo.
-
Main features considered for this release:
- Wiki Engine refactoring
- Improved user/session system
- Pluggable user-directory provider (#2456)
- Improved "ticket monitoring"
- Optional form-based login
- Improved notification architecture
- Improved ticket query system (so that it can be used instead of SQL reports system in 99% of the use cases)
- Better help/documentation system (#2656) - TracDev/Proposals/NewHelp
- Planned API changes:
- Improved rendering layer (#3332)
- Improved user/group API
In the works:
- r6986: Internationalization support
- MultipleRepositorySupport
- SearchRefactoring
- WikiRename
- TracSqlAlchemy: Experiment with SQLAlchemy for database interfacing and connection pooling (see sandbox/sqlalchemy-ng)
Revision Log
log:trunk@6942:head more details.
-
Code name Romero
- Support for multiple projects
- basic support for multiple projects
- project index and summary page (#1)
- common timeline, common search
- AdvancedSearch
- Enhanced underlying data model (GenericTrac, TracDev/Proposals/Journaling, #1890)
- Vastly improved versioncontrol subsystem (see VcRefactoring)
- Improved API for request handlers (see sandbox/controller and the newer VcRefactoring/Controller experiment)
- 'My Summary' (#150)
- Support for multiple projects
-
- Incorporate alien technology
-
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.
