{{{#!div style="float: right; margin: 0 1em"
← [../0.12] | [../0.14] →
}}}
= Release Notes for Trac [milestone:0.13] ''Cell'' Release =
{{{#!comment
== Code Name

The [milestone:0.11] release was dubbed "Genshi" and [milestone:0.12] "Babel", 
after the names of the Python packages that became closely associated to these Trac versions.
Since we don't plan to add such another new strong dependency in the near future, it's about time 
to go back to our age long tradition of picking a zombie related code name, following up to 
[milestone:0.6] "Solanum", [milestone:0.7], "Fulci", [milestone:0.8] "Qualia", 
[milestone:0.9] "Vodun", and [milestone:0.10] "Zengia" :-)

Let's keep the good input as ideas for the later releases:

 - ** "Cell" -- cboos **  0.13
 - "Datura" -- itamarost
 - "Austen" -- yaelg
 - "Algol" -- trbs
 - "Stubbs" -- cm

(the winner will get a slot in the THANKS file, a free copy of Trac 0.13, or some other equally useful gift ;-) )

Ok, so I won, not so surprisingly :-)
}}}
[[PageOutline(2-3)]]

== Highlights == 
 * ...

== Outstanding Wiki

The quest for an ultimate Wiki engine will continue, on several fronts:
 - improvements to the syntax (TracDev/Proposals/AdvancedWikiFormatting), with among other things getting a WikiCreole support as good as possible
 - build a wiki parse tree to enable all kinds of manipulation (extracting links, accessing data, getting the outline) and make formatting independent of the parsing (format to html, text, docutils intermediate representation) - see WikiEngine
 - improvements to the user interface, like better hierarchy navigation, section editing and advanced operations like branching, merging and improved rename (see TracDev/Proposals/AdvancedWikiOperations).

== Multiple Project Support

There is little doubt this is the [SeaChange/WhatUsersWant#Voteforyourpreferedpluginfunctionality most wanted feature] for Trac.
The ability to create lightweight projects from within a single Trac instance, to better match complex development environments where new products, plugins or implementations sub-projects appear and disappear over time would quite certainly be appealing to a lot of current and potential users of Trac. Many users in need of this feature have actually been forced to switch to alternative solutions more flexible in that aspect (e.g. RedMine).

For a long time, this has been thought as a "post-1.0" feature, but instead of waiting for this hypothetical long term achievement, we should actually start to think about getting there incrementally. The MultipleRepositorySupport added in [milestone:0.12] was actually a very important step in this direction, as it already makes it possible for each project to have its specific repository (or set of repositories). See TracDev/Proposals/MultipleProject for some early discussion on this topic.

Like it was the case for the MultipleRepositorySupport, MultipleProjectSupport should have no impact on users who won't use it.

== Jinja2 Support

We've decided some time ago to remove support for the ClearSilver template engine, in 0.12, but this didn't happen yet. Clearsilver had its share of inconveniences, enough that we decided to switch to the nicer Genshi template engine in 0.12, but it was **very** fast and memory lenient. While we managed to keep Genshi memory usage somewhat in control (remember #6614), the speed was never really adequate, especially for big changesets and for displaying source files over a few thousand lines of code (see TracDev/Performance#Genshi for details).

So one solution would be to switch once again, to a template engine that would combine the advantages of Genshi (pure Python, nice templates, flexible) and ClearSilver (speed!). Such a beast seems to exist now: **[http://jinja.pocoo.org/2/documentation/ Jinja2]**.

The switch can happen progressively, instead of removing support for ClearSilver we could substitute that code by the support for Jinja2 (well, maybe, remains to be seen if that still makes sense while coding it).

Several points remain to be clarified: what will be the upgrade path for plugins that came to rely on `IStreamFilter`s, how to handle themeing, should we rewrite tag builders or use lightweight string templates, etc.

See also: googlegroups:trac-dev:fc8d8c0447140110


== Detailed User Visible Changes ==
{{{#!comment
=== Wiki ===

=== Ticket System ===

==== Roadmap and Milestone ====

==== Custom Queries ====

==== Reports ====

=== Repository Browser ===

=== User Preferences ===

=== Timeline ===

=== Admin ===

=== Others ===
}}}
=== Caveats ===
{{{#!comment
 - This release requires a '''database upgrade''' when upgrading 
   from the 0.11.x series:
   {{{
   trac-admin $TRAC_ENV upgrade
   }}}
}}}
 - PySqlite 1.1.x is no longer supported; use PySqlite 2 
   (requires version >= 2.5.5 or < 2.5.2, see #9434 for details)

== Developer-visible changes ==

A detailed view of the API changes since 0.12.x can be found in [[TracDev/ApiChanges/0.13]].


== Acknowledgements ==

Many thanks to the growing number of people who have, and continue to,
support the project. Also our thanks to all people providing feedback and bug
reports that helps us making Trac better, easier to use and more effective.

Without your invaluable help, Trac would not evolve. Thank you all.

Finally, we offer hope that Trac will prove itself useful to like-minded
programmers around the world, and that this release will prove an improvement
over the last version.

Please let us know. :-)

//The TracTeam http://trac.edgewall.org //