Roadmap

Code name Incognito

• First public release
• Open Source project published
• Mailing list available

• Bugfix releases and minor feature improvements

• Bugfix releases and minor feature improvements
• More and better(?) documentation (TracGuide)

Code name Solanum

• RSS support
• Full search capability.
• Advanced reports, colored, grouped.
• RestructuredText support.
• Much more polished.
• No database changes.

Code name 245 Trioxin

• Bug fixes, minor improvements
• Improved ease-of-installation

Code name Fulci

• Major changes to database. Automatic upgrades.
• Ticket and wiki page attachments.
• Optional standalone mode (tracd).
• Email notification and integration. See TracNotification.
• Major usability overhaul.
• Syntax coloring. See TracSyntaxColoring.
• Windows installer.

Code name Argento

• Bugfix release.
• Experimental support for mod_python

Code name Qualia

• Roadmap module.
• Support for custom ticket properties.
• Wiki administration features.
• Advanced ticket queries.
• Improved diff display.
• User preferences.
• Wiki editing (near-wysiwyg) aids à la wikipedia.

Bugfix release.

Bugfix release, primarily to fix compatibility with Subversion 1.2.

Bugfix release.

Code name Vodun

• Improved modularity and extendibility (see TracPluggableModules)
• Basic database independence (#126), with preliminary support for ​PostgreSQL.
• Redesigned ticket query interface.
• Enhanced support for Subversion (copy and move operations in changesets, improved revision log viewing)
• Native Python diff support (not dependent on the diff command line utility).
• Experimental FastCGI front-end.

Tag

Release tagged tags/trac-0.9​ in r2438.

Maintenance branch

branches/0.9-stable​ created in r2437.

Revision Log

log:trunk@1295:2450

Latest Stable

0.9.6

Bug fix release.

Fixed SQL injection vulnerability in ticket query module.

Last committed change on 0.9-stable was r2588. Tagged as 0.9.1 in r2589.

Revision Log: log:branches/0.9-stable@2437:2588

Bug fixes:

• Fixed SQL injection vulnerability in search module, reported by David James and Michelle Levesque. This vulnerability is specific to PostgresQL/Trac.
• Fixed broken ticket email notifications.

Last commit on 0.9-stable was r2613. Release tagged in r2615.

Revision Log: log:branches/0.9-stable@2597:2613

Bugfixes and minor enhancements.

Warning to plugin authors: HTML escaping is now performed automatically on strings given to the template engine

From now on, the template engine code will automatically HTML escape all the strings placed in the HDF. Any HDF content that should not be escaped has to be wrapped by an instance of the new trac.util.Markup class.
Plugins have to be upgraded accordingly, otherwise double escaping will probably occur.

Release tagged in r2743.

Revision Log: log:branches/0.9-stable@2624:2741

Bugfix release.

Release tagged in r2917.

Revision Log: log:branches/0.9-stable@2744:2916

Bugfix release

Release tagged in r3202.

Revision Log: log:branches/0.9-stable@2918:3201

Latest stable version for the 0.9.x release line.

Tagged as source:tags/trac-0.9.6​
Revision Log: log:branches/0.9-stable@3203:3510
Patch for 0.9.5

Code name Zengia

• Support for database and version control backends as third-party plugins (see VersioningSystemBackend and DatabaseBackend)
• Improved notification system (see TracNotification)
• Advanced diff support (see TracChangeset)
• InterWiki and InterTrac support
• Use WSGI as web-frontend protocol
• Use unicode internally (TracDev/UnicodeGuidelines)
• Hooks for spam filtering (SpamFilter)
• Experimental MySQL database support (#986)

Revision Log

log:trunk@2450:3801

Last Stable Release for 0.10.x

0.10.5

This Trac site was running 0.10 after 2006-09-28, and probably during the whole month of October ;)

Tags

See also: TracDev/ReleaseNotes/0.10 and TracDev/ApiChanges/0.10

There's no corresponding release for this milestone - last 0.9.x release was 0.9.6.

See Revision Log or the patch for 0.9.6.

Security and bug fix release.

Revision Log:

log:branches/0.10-stable@3802:4187

Tag:

source:tags/trac-0.10.1​

Note: this release introduced two new issues (#3996 and #4120). See the follow-up 0.10.2 release.

Bug fix release.

This will be a quick follow-up to 0.10.1, aiming to fix the issues introduced there (most notably #3996 and #4120).

Revision Log:

log:branches/0.10-stable@4187:4266

Tag:

source:tags/trac-0.10.2​

Note: this release still has a bug related to the Timeline, when Apache/prefork is the server. See #4132, which is already fixed in the source:branches/0.10-stable​ line (i.e. upgrade to r4303).

Bug fixes and minor improvements.

This release contains a few critical bug fixes:

• #4132 NoSuchChangeset exception in the Timeline
• #3645 Timeout error in MySQL connections (confirmed, see also MySqlDb)

Revision Log:

log:branches/0.10-stable@4267:4445

Tag:

source:tags/trac-0.10.3​

We'll aim for a fully functional MySQL backend for the next bugfix release (0.10.4).

Bug fixes and minor improvements.

• Repository cache improvements:
  • More robust repository cache synchronizing (see #3837, #4043 and #4586)
  • Improved trac-admin resync command (see #1892 and #4797)
• Fix a possible freeze under heavy load (see #4465)
• Improved MySQL support
  • Better documentation for MySQL support (see MySqlDb)
  • Slightly improved key size for the revision index, but the limitation is still there (see #3676)
• Several other minor fixes

Note: this release needs an upgrade (trac-admin $TRAC_ENV upgrade)

If for some reason you need to downgrade to 0.10.3 afterwards, you could easily do so by running sqlite3 $TRAC_ENV/db/trac.db "update system set value=19 where name='database_version'"

Revision Log:

log:branches/0.10-stable@4447:5235

Tag:

source:tags/trac-0.10.4​

See TracDownload for the release files.

Latest stable version for the 0.10.x release line

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

Changes: log:branches/0.10-stable@5237:7229

See TracDownload for the release files.

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 permissions, 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)

For more details, see:

• TracDev/ReleaseNotes/0.11 for a summary of the user visible changes
• TracDev/ApiChanges/0.11 for a summary of the developer visible changes

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 (see TracUpgrade), so keep a backup at hand ;-)

Revision Log:

log:branches/0.11-stable:7235-3804

Tag:

source:tags/trac-0.11​ (r7236)

See TracDownload for the release files.

Bug fixes and minor improvements to 0.11.

See TracChangeLog@95#a0.11.1.

MySqlDb support has also much improved with this version.

Revision Log:

log:branches/0.11-stable:7237-7449

Tag:

source:tags/trac-0.11.1​ (r7451)

See TracDownload for the release files.

Bug fixes and minor improvements.

See TracChangeLog@95#a0.11.2.1.

Note for Python 2.3 users: you'll actually need the 0.11.2.1 version. Users of Python 2.4+ can keep using 0.11.2.

Revision Log:

log:branches/0.11-stable:7452-7662

Tags:

source:tags/trac-0.11.2​
source:tags/trac-0.11.2.1​
diff:tags/trac-0.11.2//tags/trac-0.11.2.1

See TracDownload for the release files.

Bug fixes and minor improvements.

See TracChangeLog@95#a0.11.3.

Note for Python 2.3 users: you'll actually need the r7903 fix. Users of Python 2.4+ can keep using 0.11.3.

Revision Log:

log:branches/0.11-stable@7898:7665

Tags:

source:tags/trac-0.11.3​

See TracDownload for the release files.

Bug fixes and minor improvements.

This release mainly addresses the regressions introduced in 0.11.3.

See TracChangeLog@95#a0.11.4.

Revision Log:

log:branches/0.11-stable@7666:7996

Tags:

source:tags/trac-0.11.4​

See TracDownload for the release files.

0.10.5 was the last stable release on the 0.10.x development line.

Note: No 0.10.6 release is actually planned, and unless there's a critical security issue that needs to be fixed, there won't be (i.e. the branches/0.10-stable​ branch is frozen).

Bug fixes and minor improvements.

See TracChangeLog@95#a0.11.5.

Revision Log:

log:branches/0.11-stable@7997:8363

Tags:

source:tags/trac-0.11.5​

Bug fixes and minor improvements.

See TracChangeLog@95#a0.11.6.

Adding MultipleRepositorySupport to Trac.

sandbox/multirepos@9124

This branch is now integrated in trunk (r9125).

See 0.12/TracRepositoryAdmin for details about the new features.

Last stable version for the 0.11.x release line

Bug fixes and minor improvements.

This will likely remain the last release on 0.11-stable. Focus is now on 0.12.

See TracChangeLog@95#a0.11.7.

Highlights of this release

• i18n support and interface localizations
• Multiple repository support (0.12-multirepos)
• Improved ticket query system
• Improved WikiFormatting
• Various usability improvements for the timeline, the wiki and ticket editors, and the repository browser

See the TracDev/ReleaseNotes/0.12 for a more detailed list. Note also that the TracGuide pages are now updated for 0.12.

Installation Prerequisites

Python 2.4, 2.5, 2.6 or 2.7 is needed.

• Genshi's ​0.6 is required
• Babel [babel:wiki:Download#LatestRelease:0.9.5 0.9.5] is needed if you want localization support
• Be sure to read TracUpgrade and TracInstall (notably be sure to use a recent pysqlite ≥ 2.5.5 if you need upgrade existing 0.11 environments)

Plugin writers will also find a detailed record of the API changes in TracDev/ApiChanges/0.12.

0.11.7 was the last stable release on the 0.11.x development line. 0.11-stable

Note: No 0.11.8 release is actually planned, and unless there's a critical security issue that needs to be fixed, there won't be (i.e. the branches/0.11-stable​ branch is frozen).

Bug fixes and minor improvements.

See TracChangeLog#a0.12.1.

Bug fixes and minor improvements.

See TracChangeLog#a0.12.2 for the highlights.

See TracChangeLog#a0.12.3 for the highlights.

Tagged: tags/trac-0.12.3

Tagged: tags/trac-0.12.4

First stable version for the 1.0.x release line

What's special about 1.0?

The switch to the 1.0 number was mainly done to signal a change in the release process with frequent releases of both maintenance and development versions. In effect, once 1.0 gets released, we'll create a 1.0-stable​ branch for the next-stable-1.0.x line of development for maintenance releases (1.0.1, 1.0.2, etc.), whereas trunk will be dedicated to the next-dev-1.1.x line of development and we'll make development preview releases from there (1.1.1, 1.1.2, etc.). See the RoadMap page for more details.

Installation Prerequisites

Python 2.5, 2.6 or 2.7 is needed, as support for Python 2.4 has been dropped.

Otherwise, the requirements are the same as those for 0.12:

• Genshi's ​0.6 is required
• Babel [babel:wiki:Download#LatestRelease:0.9.6-2011-03-17 0.9.6] is needed and needs to be installed first if you want to enjoy localization support
• Be sure to read TracUpgrade and TracInstall

Highlights of this release

See the TracDev/ReleaseNotes/1.0. The main TracGuide now contains the updated user and administrator documentation. Trac 1.0 will also be the first release to feature some API documentation! Plugin writers will also find a detailed list of the API changes in TracDev/ApiChanges/1.0.

This release requires an environment upgrade.

This Trac instance is using Trac 1.0, Genshi 0.7dev-r1134 and Babel 0.9.6

Tagged: tags/trac-1.0

Note that there will actually be no 0.13 version, as we're going to release 1.0 instead

Tagged: tags/trac-0.12.5

See the release notes.

Tagged: tags/trac-1.0.1

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.1.1

See the release notes.

Tagged: tags/trac-1.0.2

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.1.2

Tagged: tags/trac-0.12.6

See the release notes.

Tagged: tags/trac-1.0.3

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.1.3

See the release notes.

Tagged: tags/trac-1.0.4

See the release notes.

Tagged: tags/trac-1.0.5

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.1.4

Maintenance for 0.12.x is closed, only major issues and security issues will be fixed. Tickets to be fixed on 0.12.x should be assigned to an active milestone (e.g. 0.12.8)

Codeline: branches/0.12-stable

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.1.5

See the release notes.

Tagged: tags/trac-1.0.6

Latest stable version for the 0.12.x release line

See the release notes.

Tagged: tags/trac-0.12.7

See the release notes.

Tagged: tags/trac-1.0.7

Latest development version for the 1.1.x release line

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.1.6

See the release notes.

Tagged: tags/trac-1.0.8

See the release notes.

Tagged: tags/trac-1.0.9

See the release notes.

Top Translations messages.pot:

Top Translations messages-js.pot:

Top Translations tracini.pot:

Tagged: tags/trac-1.0.10

See the release notes.

Top Translations messages.pot:

Top Translations messages-js.pot:

Top Translations tracini.pot:

Tagged: tags/trac-1.0.11

See the release notes.

Top Translations messages.pot:

Top Translations messages-js.pot:

Top Translations tracini.pot:

Tagged: tags/trac-1.0.12

See the release notes.

Top Translations messages.pot:

Top Translations messages-js.pot:

Top Translations tracini.pot:

Tagged: tags/trac-1.0.13

First stable version release

Installation Prerequisites

Python 2.6 or 2.7 is needed, as support for Python 2.5 has been dropped.

Otherwise, the requirements are the same as those for 0.12:

• Genshi's ​0.6 is required
• Babel ≥ 0.9.5 is needed and must be installed first if you want localization support
• Be sure to read TracUpgrade and TracInstall

Tagged: tags/trac-1.2

Python 2.7 is now mandatory. Genshi is still the template engine of choice.

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.3.1

See the release notes.

Tagged: tags/trac-1.2.1

See the release notes.

Top Translations messages.pot:

Top Translations messages-js.pot:

Top Translations tracini.pot:

Tagged: tags/trac-1.0.14

See the release notes.

Top Translations messages.pot:

Top Translations messages-js.pot:

Top Translations tracini.pot:

Tagged: tags/trac-1.0.15

See the release notes.

Tagged: tags/trac-1.2.2

Python 2.7 is now mandatory. Jinja2 is the template engine of choice, but there is still support for Genshi.

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.3.2

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)

_{demo-0.12 is running r14164}

Codeline: branches/0.12-stable

See the release notes.

Top Translations messages.pot:

Top Translations messages-js.pot:

Top Translations tracini.pot:

Tagged: tags/trac-1.0.17

Python 2.7 is now mandatory. Jinja2 is the template engine of choice, but there is still support for Genshi.

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.3.3

See the release notes.

Tagged: tags/trac-1.2.3

See the release notes.

Tagged: tags/trac-1.2.4

Python 2.7 is now mandatory. Jinja2 is the template engine of choice, but there is still support for Genshi.

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.3.4

Python 2.7 is now mandatory. Jinja2 is the template engine of choice, but there is still support for Genshi.

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.3.5

See the release notes.

Top Translations messages.pot:

Top Translations messages-js.pot:

Top Translations tracini.pot:

Tagged: tags/trac-1.0.18

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 once you're sure you're going to implement it for that release

Codeline: branches/1.0-stable​

Latest development version for the 1.3.x release line

Python 2.7 is now mandatory. Jinja2 is the template engine of choice, but there is still support for Genshi.

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.3.6

See the release notes.

Tagged: tags/trac-1.2.5

First stable release

Installation Prerequisites

Python 2.7 is needed, as support for Python 2.6 has been dropped.

Otherwise, the requirements are:

• ​Jinja2 ≥ 2.9.3 is required
• Genshi ≥ ​0.7 is optional
• Babel ≥ 0.9.5 is needed and needs to be installed first for localization support
• Be sure to read TracUpgrade and TracInstall

Tagged: tags/trac-1.4

Latest stable version for the 1.0.x release line

See the release notes.

Top Translations messages.pot:

Top Translations messages-js.pot:

Top Translations tracini.pot:

Tagged: tags/trac-1.0.19

Installation Prerequisites

Python 2.7 is needed, as support for Python 2.6 has been dropped.

Otherwise, the requirements are:

• ​Jinja2 ≥ 2.9.3 is required
• Genshi ≥ ​0.7 is optional
• Babel ≥ 0.9.5 is needed and needs to be installed first for localization support
• Be sure to read TracUpgrade and TracInstall

Tagged: tags/trac-1.4.1

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-dev-1.5.x
• Move stuff to the current maintenance release once you're sure you're going to implement it for that release

Codeline: branches/1.2-stable​

Python 2.7 the only supported Python verison. This will be the only release to support Python 2.7. Future 1.5.x release will support Python 3.5+. Jinja2 is the template engine, Genshi is no longer supported.

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.5.1

Installation Prerequisites

Python 2.7 is needed, as support for Python 2.6 has been dropped.

Otherwise, the requirements are:

• ​Jinja2 ≥ 2.9.3 is required
• Genshi ≥ ​0.7 is optional
• Babel ≥ 0.9.5 is needed and needs to be installed first for localization support
• Be sure to read TracUpgrade and TracInstall

Tagged: tags/trac-1.4.2

Latest stable version for the 1.0.x release line

See the release notes.

Top Translations messages.pot:

Top Translations messages-js.pot:

Top Translations tracini.pot:

_{demo-1.0 is running 1.0.20}

Tagged: tags/trac-1.0.20

Latest stable version for the 1.2.x release line

See the release notes.

_{demo-1.2 is running 1.2.6}

Tagged: tags/trac-1.2.6

Python 2.7 the only supported Python verison. This will be the only release to support Python 2.7. Future 1.5.x release will support Python 3.5+. Jinja2 is the template engine, Genshi is no longer supported.

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.5.1

Installation Prerequisites

Python 2.7 is needed, as support for Python 2.6 has been dropped.

Otherwise, the requirements are:

• ​Jinja2 ≥ 2.9.3 is required
• Genshi ≥ ​0.7 is optional
• Babel ≥ 0.9.5 is needed and needs to be installed first for localization support
• Be sure to read TracUpgrade and TracInstall

_{demo-1.4 is running 1.4.3}

Tagged: tags/trac-1.4.3

Python 3.5+ is supported. Python 2.7 is no longer supported. Jinja2 is the template engine, Genshi is no longer supported.

See also corresponding drafts for API changes and release notes.

Tagged: tags/trac-1.5.3

Latest development version for the 1.5.x release line

Python 3.5+ is supported. Python 2.7 is no longer supported. Jinja2 is the template engine, Genshi is no longer supported.

See also corresponding drafts for API changes and release notes.

Lastest stable release

Installation Prerequisites

Python 2.7 is needed, as support for Python 2.6 has been dropped.

Otherwise, the requirements are:

• ​Jinja2 ≥ 2.9.3 is required
• Genshi ≥ ​0.7 is optional
• Babel ≥ 0.9.5 is needed and needs to be installed first for localization support
• Be sure to read TracUpgrade and TracInstall

_{demo-1.4 is running 1.4.4}

Tagged: tags/trac-1.4.4

Lastest stable release

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