Changes between Version 7 and Version 8 of TracUpgrade

Timestamp:

Jul 5, 2016, 9:22:38 AM (8 years ago)

Author:

trac

Comment:

--

TracUpgrade

@@ -42 +42 @@
 }}}
 
-This command will do nothing if the environment is already up-to-date.
+This command will not have any effect if the environment is already up-to-date.
 
 Note that a backup of your database will be performed automatically prior to the upgrade. 
-This feature is relatively new for PostgreSQL or MySQL databases, so if it fails, you will have to backup the database manually. Then, to perform the actual upgrade, run:
+This feature is relatively new for PostgreSQL or MySQL databases, so if it fails, you will have to backup the database manually. Then, to perform the actual upgrade:
 {{{#!sh
 trac-admin /path/to/projenv upgrade --no-backup
@@ -65 +65 @@
 trac-admin /path/to/env deploy /deploy/path
 }}}
+
 this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`.
 
@@ -77 +78 @@
 
 ===== Python 2.4 no longer supported
+
 Upgrade Python to at least 2.5, but not 3.0.
 
@@ -106 +108 @@
 
 ===== Python 2.3 no longer supported
+
 The minimum supported version of Python is now 2.4.
 
 ===== SQLite v3.x required
+
 SQLite v2.x is no longer supported. If you still use a Trac database of this format, you'll need to convert it to SQLite v3.x first. See [trac:PySqlite#UpgradingSQLitefrom2.xto3.x] for details.
 
 ===== [trac:PySqlite] 2 required
+
 [trac:PySqlite] 1.1.x is no longer supported. Please install 2.5.5 or later if possible, see [#Tracdatabaseupgrade Trac database upgrade] below.
 
@@ -130 +135 @@
 
 ===== Multiple Repository Support
+
 The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration.
 
@@ -143 +149 @@
 
 ===== Improved repository synchronization
+
 In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories.
 
@@ -150 +157 @@
 
 ===== Authz permission checking
+
 The authz permission checking has been migrated to a fine-grained permission policy. If you use authz permissions (aka `[trac] authz_file` and `authz_module_name`), you must add `AuthzSourcePolicy` in front of your permission policies in `[trac] permission_policies`. You must also remove `BROWSER_VIEW`, `CHANGESET_VIEW`, `FILE_VIEW` and `LOG_VIEW` from your global permissions with `trac-admin $ENV permission remove` or the "Permissions" admin panel.
 
 ===== Microsecond timestamps
+
 All timestamps in database tables, except the `session` table, have been changed from "seconds since epoch" to "microseconds since epoch" values. This change should be transparent to most users, except for custom reports. If any of your reports use date/time columns in calculations (e.g. to pass them to `datetime()`), you must divide the values retrieved from the database by 1'000'000. Similarly, if a report provides a calculated value to be displayed as a date/time (i.e. with a column named "time", "datetime", "changetime", "date", "created" or "modified"), you must provide a microsecond timestamp, that is, multiply your previous calculation with 1'000'000.
 
 ==== Upgrading from Trac 0.10 to Trac 0.11
+
 ===== Site Templates and Styles
+
 The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information.
 
@@ -162 +173 @@
 
 ===== Trac Macros, Plugins
+
 The Trac macros will need to be adapted, as the old-style wiki-macros are not supported anymore due to the drop of [trac:ClearSilver] and the HDF. They need to be converted to the new-style macros, see WikiMacros. When they are converted to the new style, they need to be placed into the plugins directory instead and not wiki-macros, which is no longer scanned for macros or plugins.
 
 ===== For FCGI/WSGI/CGI users
+
 For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file:
 {{{#!sh
@@ -177 +190 @@
 ===== New Default Configurable Workflow
 
-When you run `trac-admin <env> upgrade`, your `trac.ini` will be modified to include a `[ticket-workflow]` section. The workflow configured in this case is the original workflow, so that ticket actions will behave like they did in 0.10.
-
-Graphically, that looks like this:
+When you run `trac-admin <env> upgrade`, your `trac.ini` will be modified to include a `[ticket-workflow]` section. The workflow configured in this case is the original workflow, so that ticket actions will behave like they did in 0.10:
 
 {{{#!Workflow width=500 height=240
@@ -243 +254 @@
 === Changing Database Backend
 
-The [http://trac-hacks.org/wiki/TracMigratePlugin TracMigratePlugin] on [http://trac-hacks.org trac-hacks.org] has been written to assist in migrating between SQLite, MySQL and PostgreSQL databases.
+The [https://trac-hacks.org/wiki/TracMigratePlugin TracMigratePlugin] on [https://trac-hacks.org trac-hacks.org] has been written to assist in migrating between SQLite, MySQL and PostgreSQL databases.
 
 === Upgrading from older versions of Trac #OlderVersions