Changes between Version 3 and Version 4 of TracUpgrade

Timestamp:

Jan 30, 2019, 11:46:21 PM (5 years ago)

Author:

trac

Comment:

--

TracUpgrade

@@ -20 +20 @@
 
 {{{#!sh
-easy_install --upgrade Trac
+easy_install --upgrade Trac==1.2
 }}}
 
@@ -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. The backup will be saved in the location specified by `[trac]` `backup_dir`.
+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
+}}}
 
 === 4. Update the Trac Documentation === #UpdatetheTracDocumentation
@@ -55 +59 @@
 === 5. Refresh static resources
 
-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]:
+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:
 {{{#!sh
 trac-admin /path/to/env deploy /deploy/path
 }}}
 
-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.
+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.
 {{{#!comment
 Remove above note once #9936 is fixed.
-}}}
 }}}
 
@@ -92 +94 @@
 ===== New workflow actions #NewWorkflowActions
 
-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.
+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.
 
 ===== New permissions policy for read-only wiki pages
@@ -117 +119 @@
 
 * [https://trac-hacks.org/wiki/BatchModifyPlugin BatchModifyPlugin]
-* [https://trac-hacks.org/wiki/GitPlugin GitPlugin]
+* ​[https://trac-hacks.org/wiki/GitPlugin GitPlugin]
 * [https://trac-hacks.org/wiki/OverrideEditPlugin OverrideEditPlugin]
 
@@ -159 +161 @@
 
 * [https://trac-hacks.org/wiki/AutoQueryPlugin AutoQueryPlugin]
-* [https://trac-hacks.org/wiki/AdminConsoleProviderPatch AdminConsoleProviderPatch]
+* ​[https://trac-hacks.org/wiki/AdminConsoleProviderPatch AdminConsoleProviderPatch]
 * [https://trac-hacks.org/wiki/AnchorMacro AnchorMacro]: see WikiFormatting#SettingAnchors
 * [https://trac-hacks.org/wiki/TicketChangePlugin TicketChangePlugin]: see [TracPermissions#TicketSystem TICKET_EDIT_COMMENT permission]
@@ -246 +248 @@
 }}}
 
-There are some significant caveats in this, such as accepting a ticket sets it to 'assigned' state, and assigning a ticket sets it to 'new' state. So you will probably want to migrate to "basic" workflow; [trac:source:branches/1.2-stable/contrib/workflow/migrate_original_to_basic.py contrib/workflow/migrate_original_to_basic.py] may be helpful. See TracWorkflow for a detailed description of the new basic workflow.
+There are some significant caveats in this, such as accepting a ticket sets it to 'assigned' state, and assigning a ticket sets it to 'new' state. So you will probably want to migrate to "basic" workflow; [trac:source:trunk/contrib/workflow/migrate_original_to_basic.py contrib/workflow/migrate_original_to_basic.py] may be helpful. See TracWorkflow for a detailed description of the new basic workflow.
 
 === 7. Restart the Web Server #RestarttheWebServer
@@ -258 +260 @@
 Trac supports customization of its Genshi templates by placing copies of the templates in the `<env>/templates` folder of your [TracEnvironment environment] or in a common location specified in the [[TracIni#GlobalConfiguration| [inherit] templates_dir]] configuration setting. If you choose to do so, be aware that you will need to repeat your changes manually on a copy of the new templates when you upgrade to a new release of Trac (even a minor one), as the templates will likely evolve. So keep a diff around.
 
-The preferred way to perform TracInterfaceCustomization is to write a custom plugin doing an appropriate `ITemplateStreamFilter` transformation, as this is more robust in case of changes: we usually won't modify an element `id` or change its CSS `class`, and if we have to do so, this will be documented in the [trac:TracDev/ApiChanges] pages.
+The preferred way to perform TracInterfaceCustomization is to write a custom plugin doing an appropriate `ITemplateStreamFilter` transformation, as this is more robust in case of changes: we usually won't modify element `id`s or change CSS `class`es, and if we have to do so, this will be documented in the [trac:TracDev/ApiChanges] pages.
 
 === !ZipImportError