This is a page to makes notes about upgrading Trac from 0.10.x to 0.11.x
Our current Trac setup is based on [http://trac.edgewall.org/wiki/TracMultipleProjects/MultipleEnvironmentsSingleDatabase].
Upgrade Existing Environments
Off hand a I don't believe this can be done automatically (trac-admin --upgrade), but we can use the 0.11 upgrade method as a base for this, it shouldn't be very messy, just adapting to handle the dbuser column.
Upgrade Postgres Views
The views have four areas, Insert, Delete, Modify, and Select. These are more aptly called Rules. The select is the simplest since it just adds a filter on the username, the others modify the SQL statement being made to include the username. The current rules in SQL form HERE give us how Postgres expects them to look, we just need to add new ones for any new tables, or adjust the old ones for any different columns/column names.
Upgrade SQL template
Normally Trac initializes the project with a set of wiki pages from the default wiki page directory, since we do our initialization in the beaversource.py module, we need to upgrade the SQL that it uses. This would basically mean copying the contents of the pages in the 0.11 wiki-default directory into the SQL statements that contain the old data in archive/beavertrac/trac_data.sql. Also don't forget to remove pages that are no longer used, like WikiMacro and add any new pages.
Upgrade ini template
This part I'm a little rusty on, but I believe we either completely override, or just amend to, the ini that trac creates, if we do, its this file management/bs-admin/trunk/beaversource.ini-dist. Since 0.11 adds new sections and such, we'll need to modify this. Also, Trac 0.11 supports an inherit section that we'll want to make use of in our theming. If I'm not mistaken, this will allow us to have a theme in one project or central location that all projects use, and would be upgrade-safe.
