Roadmap
-
Highlights of this release:
- i18n and localizations
- Multiple repository support (0.12-multirepos)
- Improved ticket query system
- Improved Wiki formatting
- Various usability improvements for the timeline, the wiki and ticket editors, and the repository browser
See 0.12 for the updated parts of the Trac guide. Those wiki pages describe most of the new features.
Prerequisites:
- Genshi's trunk is required ( [G1072] or more recent)
- Babel 0.9.4 is needed if you want localization support, otherwise it's optional
- Be sure to read 0.12/TracUpgrade and 0.12/TracInstall for the specific installation instructions for this version
See also:
- Build Status
- TracDev/ReleaseNotes/0.12 for the user visible changes
- TracDev/ApiChanges/0.12 for the developer visible changes
- Detailed Revision Log
- 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.
-
Possible main features:
- 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
Experimental:
- TracDev/Proposals/NewHelp (#2656) - newhelp
- TracSqlAlchemy: experiment with SQLAlchemy for database interfacing and connection pooling (see sandbox/sqlalchemy-ng)
-
Tickets coming from 0.12 which are not essential for the 0.12 release.
-
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.
- #130
- Multi-project support
- #1242
- [ER] Generalized automatic cross-references in Trac
- #1386
- Adding properties to Wiki Pages
- #1395
- Text box for duplicate when a bug is a duplicate
- #3895
- Provide Trac API for returning all outbound links in a page
- #7871
- Add start date to a milestone
- #8137
- TracQuery count as part of a heading
- #8140
- nested lists with multiple paragraphs should work properly
- #8541
- [patch] recursive auto-expansion of folders containing only one sub-directory
- #109
- MissingLinks, an index over missing wiki pages
- #8314
- Dynamic Default Values
- #7422
- Projects, milestones, tickets improvement
-
Overview of tickets applicable to the TracMercurial plugin.
- #7160
- Problems with character encoding
- #7217
- Non-ASCII characters get replaced with '?' in changeset metadata
- #7743
- Add/document commit-hook
- #8180
- Bad encoding in mercurial plugin
- #8417
- CachedRepository support in TracMercurial
- #8538
- support non-ascii filenames in mercurial vcs backend
- #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
-
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)
OTOH, blue sky ideas are still to be targeted for 2.0.
-
Milestone: spam-filter-plugin
No date set
Overview of tickets applicable to the SpamFilter and SpamFilter/Captcha plugins.
No results
-
