Changes between Version 16 and Version 17 of TracUpgrade

Timestamp:

14/06/2017 12:47:21 (7 years ago)

Author:

trac

Comment:

--

TracUpgrade

@@ -20 +20 @@
 
 {{{#!sh
-easy_install --upgrade Trac==1.2
+easy_install --upgrade Trac
 }}}
 
@@ -42 +42 @@
 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:
-{{{#!sh
-trac-admin /path/to/projenv upgrade --no-backup
-}}}
+Note that a backup of your database will be performed automatically prior to the upgrade. The backup will be saved in the location specified by `[trac]` `backup_dir`.
 
 === 4. Update the Trac Documentation === #UpdatetheTracDocumentation
@@ -59 +55 @@
 === 5. Refresh static resources
 
-If you have set up a web server to give out static resources directly (accessed using the `/chrome/` URL) then you will need to refresh them using the same command:
+If you have configured your web server to serve static resources directly (accessed using the `/chrome/` URL) then you will need to refresh them using the [TracInstall#MappingStaticResources same command]:
 {{{#!sh
 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`.
-
-Some web browsers (IE, Opera) cache CSS and Javascript files aggressively, so you may need to instruct your users to manually erase the contents of their browser's cache, a forced refreshed (`<F5>`) should be enough.
+This will extract static resources and CGI scripts (`trac.wsgi`, etc) from the new Trac version and plugins into `/deploy/path`.
+
+{{{#!div style="border: 1pt dotted; margin: 1em"
+**Note:** Some web browsers (IE, Opera) cache CSS and Javascript files, so you should instruct your users to manually erase the contents of their browser's cache. A forced refreshed (SHIFT + <F5>) should be enough.
 {{{#!comment
 Remove above note once #9936 is fixed.
+}}}
 }}}
 
@@ -94 +92 @@
 ===== New workflow actions #NewWorkflowActions
 
-The ticket creation step is controlled with a workflow action. The default workflow has `create` and `create_and_assign` actions. The `create` action will always be added when upgrading the database. The `create_and_assign` action will be added if the workflow has an //assigned// state. You may want to edit your workflow after upgrading the database to customize the actions available on the //New Ticket// page.
+The ticket creation step is controlled with a [TracWorkflow#TicketCreateAction workflow action]. The default workflow has `create` and `create_and_assign` actions. The `create` action will always be added when upgrading the database. The `create_and_assign` action will be added if the workflow has an //assigned// state. You may want to edit your workflow after upgrading the database to customize the actions available on the //New Ticket// page.
 
 ===== New permissions policy for read-only wiki pages