Edgewall Software

Changes between Version 129 and Version 130 of TracUpgrade


Ignore:
Timestamp:
Oct 15, 2019, 6:36:25 AM (5 years ago)
Author:
trac
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • TracUpgrade

    v129 v130  
    66== Instructions
    77
    8 Typically, there are seven steps involved in upgrading to a newer version of Trac:
    9 
    10 === 1. Bring your server off-line
     8There are seven recommended steps for upgrading to a newer version of Trac:
     9
     10=== 1. Check your plugins
     11
     12Check whether your plugins are compatible with the version of Trac that you are upgrading to. Obsolete plugins listed in the [#VersionSpecificSteps version specific steps] below should be uninstalled or disabled.
     13
     14If you are upgrading to a minor release, plugin compatibility is usually not a concern because the Trac API rarely changes, and major features are usually not introduced, for minor releases.
     15
     16If your plugins are installed from [https://trac-hacks.org trac-hacks.org] you can check compatibility by looking for a tag on the project page corresponding to a major release (e.g. `1.2`). If you are unsure, you'll want to contact the plugin author or ask on the [trac:MailingList MailingList].
     17
     18If you are running several Trac plugins it is good to test the upgrade and plugin functionality in a staging instance of your site before upgrading your production instance. Remember, plugin authors are responsible for Trac version compatibility and plugins can interact in unexpected ways. Your Trac instance may have a unique combination of plugins and therefore it's advised that you do some verification testing when making any changes to your site.
     19
     20=== 2. Bring your server off-line
    1121
    1222It is not a good idea to update a running server: the server processes may have parts of the current packages cached in memory, and updating the code will likely trigger [#ZipImportError internal errors].
    1323
    14 Although a database backup will be implicitly created by default when upgrading the environment, it is always a good idea to perform a full backup of the environment using the [TracBackup hotcopy] command before beginning.
    15 
    16 === 2. Update the Trac Code #UpdatetheTracCode
    17 
    18 Get the new version as described in TracInstall, or through your operating system package manager.
    19 
    20 If you already an earlier version of Trac installed via `easy_install`, it might be easiest to also use `easy_install` to upgrade your Trac installation:
    21 
    22 {{{#!sh
    23 easy_install --upgrade Trac
    24 }}}
    25 
    26 You may also want to remove the pre-existing Trac code by deleting the `trac` directory from the Python `lib/site-packages` directory, or remove Trac `.egg` files from former versions.
    27 The location of the site-packages directory depends on the operating system and the location in which Python was installed. However, the following locations are typical:
    28  * on Linux: `/usr/lib/python2.X/site-packages`
    29  * on Windows: `C:\Python2.X\lib\site-packages`
    30  * on MacOSX: `/Library/Python/2.X/site-packages`
    31 
    32 You may also want to remove the directory in which your static resources are [TracInstall#cgi-bin deployed]. The exact location depends on your platform. This cleanup is not mandatory, but makes it easier to troubleshoot issues later on, as your installation is uncluttered by code or templates from a previous release that is not used anymore. As usual, make a backup before actually removing things.
    33 
    34 === 3. Upgrade the Trac Environment #UpgradetheTracEnvironment
    35 
    36 Environment upgrades are not necessary for minor version releases unless otherwise noted.
    37 
    38 After restarting, Trac should show the instances which need a manual upgrade via the automated upgrade scripts to ease the pain. These scripts are run via [TracAdmin trac-admin]:
    39 {{{#!sh
    40 trac-admin /path/to/projenv upgrade
     24Although a database backup will be implicitly created by default when upgrading the environment, it is always a good idea to perform a full backup of the environment using the [TracBackup hotcopy] command before beginning. You may also wish to create a full backup of your server.
     25
     26=== 3. Update Trac and dependencies #UpdatetheTracCode
     27
     28The packages are available through several channels, as described in [trac:TracDownload]. If your Trac instance was installed through an operating system package manager or an installer on Windows, proceed with the standard steps that are appropriate for your operating system.
     29
     30If you are managing your Trac installation using command line tools, `pip` is the preferred tool to upgrade a Trac instance because it will uninstall the old version. The following command will upgrade your Trac installation using the package published to [https://pypi.python.org/pypi/Trac PyPI].
     31
     32{{{#!sh
     33$ pip install --upgrade Trac
     34}}}
     35
     36The upgrade command will give you the latest release of Trac. If instead you wish to upgrade to a different version, such as a minor release of Trac when there is a newer major release available, then specify the Trac version in the `pip` command.
     37
     38{{{#!sh
     39$ pip install --upgrade Trac==1.2.1
     40}}}
     41
     42You should also upgrade dependencies so they are compliant with the [TracInstall#Dependencies required versions].
     43
     44=== 4. Upgrade the Trac Environment #UpgradetheTracEnvironment
     45
     46Environment upgrades are not necessary for minor version releases unless otherwise noted.
     47
     48On starting your web server after upgrading Trac, a message will be displayed for projects that need to be upgraded and the projects will not be accessible until the upgrade is run.
     49
     50The upgrade is run using a [TracAdmin trac-admin] command:
     51{{{#!sh
     52$ trac-admin /path/to/projenv upgrade
    4153}}}
    4254
    4355This command will not have any effect if the environment is already up-to-date.
    4456
    45 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`.
    46 
    47 === 4. Update the Trac Documentation === #UpdatetheTracDocumentation
    48 
    49 By default, every [TracEnvironment Trac environment] includes a copy of the Trac documentation for the installed version. However, to keep the included documentation in sync with the installed version of Trac, use the following [TracAdmin trac-admin] command to upgrade the documentation:
    50 {{{#!sh
    51 trac-admin /path/to/projenv wiki upgrade
    52 }}}
    53 
    54 Note that this procedure will leave your `WikiStart` page intact.
    55 
    56 === 5. Refresh static resources
    57 
    58 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]:
    59 {{{#!sh
    60 trac-admin /path/to/env deploy /deploy/path
    61 }}}
    62 
    63 This will extract static resources and CGI scripts (`trac.wsgi`, etc) from the new Trac version and plugins into `/deploy/path`.
     57It is recommended that you set the [[TracIni#logging-log_level-option|log_level]] to `INFO` before running the upgrade. The additional information in the logs can be helpful in case something unexpected occurs during the upgrade.
     58
     59Note that a backup of your database will be performed automatically prior to the upgrade. The backup is saved in the location specified by [[TracIni#trac-backup_dir-option|backup_dir]].
     60
     61=== 5. Update the Trac Documentation === #UpdatetheTracDocumentation
     62
     63By default, every [TracEnvironment Trac environment] includes a copy of the Trac documentation for the installed version. To keep the documentation in sync with the installed version of Trac, upgrade the documentation:
     64{{{#!sh
     65$ trac-admin /path/to/projenv wiki upgrade
     66}}}
     67
     68Note that this procedure will leave your `WikiStart`, `InterMapTxt` and `SandBox` pages unaltered. Local changes to other pages that are distributed with Trac will be overwritten, however these pages are read-only by default for Environments created in Trac 1.3.3 and later.
     69
     70=== 6. Refresh static resources
     71
     72If 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 deploy command]. The `deploy` command will extract static resources and CGI scripts (`trac.wsgi`, etc) from the new Trac version and plugins into `/deploy/path`.
     73{{{#!sh
     74$ trac-admin /path/to/env deploy /deploy/path
     75}}}
     76
     77Before refreshing, it is recommended that you remove the directory in which your static resources are deployed. The directory location depends on the choice you made during installation. This cleanup is not mandatory, but makes it easier to troubleshoot issues as your installation is uncluttered by unused assets from a previous release. As usual, make a backup before deleting the directory.
    6478
    6579{{{#!div style="border: 1pt dotted; margin: 1em"
    66 **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.
     80**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 sufficient.
    6781{{{#!comment
    6882Remove above note once #9936 is fixed.
     
    7084}}}
    7185
    72 === 6. Steps specific to a given Trac version
     86=== 7. Steps specific to a given Trac version #VersionSpecificSteps
     87
     88==== Upgrading from Trac 1.2 to 1.4 #to1.4
     89
     90===== Python 2.6 no longer supported
     91
     92Upgrade Python to 2.7, but not 3.0 or greater.
     93
     94===== MySQL-python no longer supported
     95
     96[https://pypi.python.org/pypi/PyMySQL PyMySQL] is the supported MySQL database library, support for [https://pypi.python.org/pypi/MySQL-python MySQL-python] has been removed.
     97
     98===== Obsolete Plugins
     99
     100Trac has added functionality equivalent to the following plugins:
     101
     102* [https://trac-hacks.org/wiki/DynamicVariablesPlugin DynamicVariablesPlugin]: dynamic variables are autocompleted
     103* [https://trac-hacks.org/wiki/NavAddPlugin NavAddPlugin]: see TracNavigation
     104* [https://trac-hacks.org/wiki/FlexibleAssignToPlugin FlexibleAssignToPlugin]: subclass `ConfigurableTicketWorkflow` and override `get_allowed_owners`
     105* [https://trac-hacks.org/wiki/TracMigratePlugin TracMigratePlugin]: Use the `trac-admin` [TracAdmin#ChangingDatabaseBackend convert_db command]
     106
     107The plugins should be removed when upgrading Trac to 1.4.
     108
     109===== Jinja2 is the new template engine
     110
     111Content is now generated by using the Jinja2 template
     112engine. You may want to verify that your plugins are
     113compatible with this change.
     114(TODO: expand...)
     115
     116If you customized the Trac templates, or the `site.html`
     117template, you'll need to adapt that as well.
     118(TODO: expand...) See [#CustomizedTemplates]
     119
     120===== New permission policies for Wiki and Ticket realms
     121
     122Since 1.3.2 there are new permission policies for the ticket and wiki systems. `DefaultTicketPolicy` allows an authenticated users with `TICKET_APPEND` or `TICKET_CHPROP` to modify the description of a ticket they reported. It also implements the pre-1.3.2 behavior of allowing users to edit their own ticket comments. [#Newpermissionspolicyforread-onlywikipages ReadonlyWikiPolicy], added in 1.1.2, is renamed to `DefaultWikiPolicy`. The new permission policies can be easily replaced with alternate implementations if the default behavior is not desired.
     123
     124If `[trac] permission_policy` has the default value `ReadonlyWikiPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy`, then `DefaultWikiPolicy, DefaultTicketPolicy` should be automatically appended to the list when upgrading the environment:
     125{{{#!ini
     126[trac]
     127permission_policies = DefaultWikiPolicy,
     128 DefaultTicketPolicy,
     129 DefaultPermissionPolicy,
     130 LegacyAttachmentPolicy
     131}}}
     132
     133If other permission policies are enabled, `trac.ini` will need to be edited to add `DefaultWikiPolicy, DefaultTicketPolicy` to `permission_policies`. See [wiki:TracFineGrainedPermissions#DefaultWikiPolicyandDefaultTicketPolicy] for additional details on the proper ordering.
     134
     135===== Description field added to ticket enums #enum-description-field
     136
     137The ticket enums now have a //description// field. An //ambiguous column name// error may be seen for reports that reference the `description` column of another table and join the `enum` table with that table (e.g. `ticket`, `component`). The reports {1}, {2}, {3}, {4}, {5}, {7}, and {8} are modified by an upgrade step to fix the issue, but the modification may not succeed if the default reports have been modified, in which case `upgrade` will output a message to the terminal instructing the user to modify the reports. User-created reports may also need to be modified.
     138
     139Reports that display the error need to be modified to prefix the `description` column with the appropriate table name or alias. For example, if the `ticket` table is aliased as `t` (`ticket t` or `ticket AS t`), replace `description` with `t.description` if the report should use the ticket's `description` column.
     140
     141===== Removed `<repostype>` and `<repospath>` arguments from TracAdmin `initenv` command
     142
     143The TracAdmin `initenv` command allowed the default repository to be specified using the third and fourth positional arguments of `initenv`:
     144{{{
     145initenv [<projectname> <db> [<repostype> <repospath>]]
     146}}}
     147
     148The arguments were an artifact of Trac < 0.12, which only supported a single repository. Trac 0.12 and later supports multiple repositories, which can be specified at the time of environment creation using the `--inherit` and `--config` arguments. See the [TracEnvironment#SourceCodeRepository initenv documentation] for details on specifying source code repositories.
    73149
    74150==== Upgrading from Trac 1.0 to 1.2 #to1.2
     
    82158Trac has added functionality equivalent to the following plugins:
    83159* [https://trac-hacks.org/wiki/AdminEnumListPlugin AdminEnumListPlugin]
     160* [https://trac-hacks.org/wiki/AttachmentNotifyPlugin AttachmentNotifyPlugin]: attachment notifications are sent in Trac 1.0.3 and later
    84161* [https://trac-hacks.org/wiki/DateFieldPlugin DateFieldPlugin]: see the **time** [TracTicketsCustomFields#AvailableFieldTypesandOptions custom field type]
    85 * [https://trac-hacks.org/wiki/GroupBasedRedirectionPlugin GroupBasedRedirectionPlugin]: the default handler can set as a user preference.
     162* [https://trac-hacks.org/wiki/FlexibleReporterNotificationPlugin FlexibleReporterNotificationPlugin]: [trac:CookBook/Notification/Subscriptions custom subscribers] can be implemented in the new extensible notification system
     163* [https://trac-hacks.org/wiki/GroupBasedRedirectionPlugin GroupBasedRedirectionPlugin]: the default handler can set as a user preference
     164* [https://trac-hacks.org/wiki/GroupingAssignToPlugin GroupingAssignToPlugin]: groups and permissions can be used in the [TracWorkflow#BasicTicketWorkflowCustomization set_owner] workflow attribute
    86165* [https://trac-hacks.org/wiki/LinenoMacro LinenoMacro]: see WikiProcessors#AvailableProcessors
    87166* [https://trac-hacks.org/wiki/NeverNotifyUpdaterPlugin NeverNotifyUpdaterPlugin]: see [TracNotification#notification-subscriber-section notification subscribers]
     
    93172===== New workflow actions #NewWorkflowActions
    94173
    95 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.
     174The 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.
    96175
    97176===== New permissions policy for read-only wiki pages
     
    117196Trac has added functionality equivalent to the following plugins:
    118197
     198* [https://trac-hacks.org/wiki/AnchorMacro AnchorMacro]
    119199* [https://trac-hacks.org/wiki/BatchModifyPlugin BatchModifyPlugin]
    120200* [https://trac-hacks.org/wiki/GitPlugin GitPlugin]
    121201* [https://trac-hacks.org/wiki/OverrideEditPlugin OverrideEditPlugin]
     202* [https://trac-hacks.org/wiki/ProgressMeterMacro ProgressMeterMacro]
    122203
    123204The plugins should be removed when upgrading Trac to 1.0.
     
    133214The upgrade procedure should take care of this and change the TracIni appropriately, unless you already had the svn components explicitly disabled.
    134215
    135 ===== Attachments migrated to new location
    136 
    137 Another step in the automatic upgrade will change the way the attachments are stored. Create a backup of the `attachments` directory before upgrading. In case the `attachments` directory contains some files which are //not// attachments, the last step of the migration to the new layout will fail: the deletion of the now unused `attachments` directory can't be done if there are still files and folders in it. You may ignore this error, but better to move them elsewhere and remove the `attachments` directory manually. The attachments themselves are now all located in your environment below the `files/attachments` directory.
     216===== Attachments migrated to new location #AttachmentsMigrated
     217
     218Another step in the automatic upgrade will change the way the attachments are stored. There have been reports that the attachment migration [#AttachmentsNotMigrated sometimes fails], so it's extra important that you [TracBackup backup your environment].
     219
     220In case the `attachments` directory contains some files which are //not// attachments, the last step of the migration to the new layout will not be completed: the deletion of the now unused `attachments` directory can't be done if there are still files and folders in it. You may ignore this error, but better to move them elsewhere and remove the `attachments` directory manually. The attachments themselves are now all located in your environment below the `files/attachments` directory.
    138221
    139222===== Behavior of `[ticket] default_owner` changed
     
    141224Prior to 1.0, the owner field of new tickets always defaulted to `[ticket] default_owner` when the value was not empty. If the value was empty, the owner field defaulted to to the Component's owner. In 1.0 and later, the `default_owner` must be set to `< default >` to make new tickets default to the Component's owner. This change allows the `default_owner` to be set to an empty value if no default owner is desired.
    142225
    143 ==== Upgrading from Trac 0.11 to Trac 0.12
    144 
    145 ===== Python 2.3 no longer supported
    146 
    147 The minimum supported version of Python is now 2.4.
    148 
    149 ===== SQLite v3.x required
    150 
    151 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.
    152 
    153 ===== [trac:PySqlite] 2 required
    154 
    155 [trac:PySqlite] 1.1.x is no longer supported. Please install 2.5.5 or later if possible, see [#Tracdatabaseupgrade Trac database upgrade] below.
    156 
    157 ===== Obsolete Plugins
    158 
    159 Trac has added functionality equivalent to the following plugins:
    160 
    161 * [https://trac-hacks.org/wiki/AutoQueryPlugin AutoQueryPlugin]
    162 * [https://trac-hacks.org/wiki/AdminConsoleProviderPatch AdminConsoleProviderPatch]
    163 * [https://trac-hacks.org/wiki/AnchorMacro AnchorMacro]: see WikiFormatting#SettingAnchors
    164 * [https://trac-hacks.org/wiki/TicketChangePlugin TicketChangePlugin]: see [TracPermissions#TicketSystem TICKET_EDIT_COMMENT permission]
    165 * [https://trac-hacks.org/wiki/TicketDeletePlugin TicketDeletePlugin]: see `tracopt.ticket.deleter`
    166 * [https://trac-hacks.org/wiki/SubversionLocationPlugin SubversionLocationPlugin]: see TracRepositoryAdmin#Repositories
    167 * [https://trac-hacks.org/wiki/WikiCreoleRendererPlugin WikiCreoleRendererPlugin]: see [trac:WikiCreole]
    168 * [https://trac-hacks.org/wiki/RepoRevisionSyntaxPlugin RepoRevisionSyntaxPlugin] (added in 0.12.1)
    169 
    170 The plugins should be removed when upgrading Trac to 0.12.
    171 
    172 ===== Multiple Repository Support
    173 
    174 The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration.
    175 
    176 This may be of interest to users with only one repository, since there is now a way to avoid the potentially costly resync check at every request.
    177 
    178 ===== Resynchronize the Trac Environment Against the Source Code Repository
    179 
    180 Each [TracEnvironment Trac environment] must be resynchronized against the source code repository in order to avoid errors such as "[trac:#6120 No changeset ??? in the repository]" while browsing the source through the Trac interface:
    181 
    182 {{{#!sh
    183 trac-admin /path/to/projenv repository resync '*'
    184 }}}
    185 
    186 ===== Improved repository synchronization
    187 
    188 In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories.
    189 
    190 While you can keep the same synchronization as in 0.11 adding the post-commit hook as outlined in TracRepositoryAdmin#Synchronization and TracRepositoryAdmin#ExplicitSync will allow more efficient synchronization and is more or less required for multiple repositories.
    191 
    192 Note that if you were using the `trac-post-commit-hook`, ''you're strongly advised to upgrade it'' to the new hook documented in the above references and [TracWorkflow#Howtocombinethetracopt.ticket.commit_updaterwiththetestingworkflow here], as the old hook will not work with anything else than the default repository and even for this case, it won't trigger the appropriate notifications.
    193 
    194 ===== Authz permission checking
    195 
    196 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.
    197 
    198 ===== Microsecond timestamps
    199 
    200 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.
    201 
    202 ==== Upgrading from Trac 0.10 to Trac 0.11
    203 
    204 ===== Site Templates and Styles
    205 
    206 The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information.
    207 
    208 If you are using custom CSS or modified templates in the `templates` directory of the TracEnvironment, you will need to convert them to the Genshi way of doing things. To continue to use your style sheet, follow the instructions at TracInterfaceCustomization#SiteAppearance.
    209 
    210 ===== Trac Macros, Plugins
    211 
    212 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.
    213 
    214 ===== For FCGI/WSGI/CGI users
    215 
    216 For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file:
    217 {{{#!sh
    218 trac-admin /path/to/env deploy /deploy/directory/path
    219 }}}
    220 
    221 This will create a deploy directory with the following two subdirectories: `cgi-bin` and `htdocs`. Then update your Apache configuration file `httpd.conf` with this new `trac.cgi` location and `htdocs` location.
    222 
    223 ===== Web Admin plugin integrated
    224 
    225 If you had the [trac:WebAdmin] plugin installed, you can uninstall it as it is part of the Trac code base since 0.11.
    226 
    227 ===== New Default Configurable Workflow
    228 
    229 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:
    230 
    231 {{{#!Workflow width=500 height=240
    232 leave = * -> *
    233 leave.operations = leave_status
    234 leave.default = 1
    235 accept = new -> assigned
    236 accept.permissions = TICKET_MODIFY
    237 accept.operations = set_owner_to_self
    238 resolve = new,assigned,reopened -> closed
    239 resolve.permissions = TICKET_MODIFY
    240 resolve.operations = set_resolution
    241 reassign = new,assigned,reopened -> new
    242 reassign.permissions = TICKET_MODIFY
    243 reassign.operations = set_owner
    244 reopen = closed -> reopened
    245 reopen.permissions = TICKET_CREATE
    246 reopen.operations = del_resolution
    247 }}}
    248 
    249 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.
    250 
    251 === 7. Restart the Web Server #RestarttheWebServer
    252 
    253 If you are not running [wiki:TracCgi CGI], reload the new Trac code by restarting your web server.
     226==== Upgrading from older versions of Trac #OlderVersions
     227
     228For upgrades from versions older than Trac 0.12, refer first to [trac:wiki:0.12/TracUpgrade#SpecificVersions TracUpgrade for 0.12].
     229
     230For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions TracUpgrade for 0.10].
    254231
    255232== Known Issues
     
    257234=== Customized Templates
    258235
    259 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.
    260 
    261 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.
     236Trac supports customization of its 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 customize the templates, be aware that you will need to repeat your changes on a copy of the new templates when you upgrade to a new release of Trac (even a minor one), as the templates will evolve. So keep a diff around.
     237
     238The preferred way to perform TracInterfaceCustomization is a custom plugin doing client-side !JavaScript transformation of the generated output, 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.
    262239
    263240=== !ZipImportError
    264241
    265 Due to internal caching of zipped packages, whenever the content of the packages change on disk, the in-memory zip index will no longer match and you'll get irrecoverable !ZipImportError errors. Better anticipate and bring your server down for maintenance before upgrading.
     242Due to internal caching of zipped packages, whenever the content of the packages change on disk, the in-memory zip index will no longer match and you'll get irrecoverable !ZipImportError errors. Better to anticipate and bring your server down for maintenance before upgrading.
    266243See [trac:#7014] for details.
    267244
     
    270247`trac-admin` will not delete or remove default wiki pages that were present in a previous version but are no longer in the new version.
    271248
    272 === Trac database upgrade
    273 
    274 A known issue in some versions of [trac:PySqlite] (2.5.2-2.5.4) prevents the trac-admin upgrade script from successfully upgrading the database format. It is advised to use either a newer or older version of the sqlite python bindings to avoid this error. For more details see ticket [trac:#9434].
    275 
    276249=== Parent dir
    277250
    278251If you use a Trac parent env configuration and one of the plugins in one child does not work, none of the children will work.
    279252
     253=== Attachments not migrated #AttachmentsNotMigrated
     254
     255There have been reports that attachments are not [#AttachmentsMigrated migrated] when upgrading to Trac 1.0 or later. The cause of the issue has not yet been found. If you encounter this issue, see [https://trac.edgewall.org/wiki/TracFaq#Q:Attachmentsaremissingafterupgrade the FAQ] for a workaround and please report your findings to [trac:#11370].
     256
    280257== Related topics
    281258
    282259=== Upgrading Python
    283260
    284 Upgrading Python to a newer version will require reinstallation of Python packages: Trac itself of course, but also [https://pypi.org/project/setuptools easy_install], if you've been using that. If you are using Subversion, you'll also need to upgrade the Python bindings for svn.
    285 
    286 ==== Windows and Python 2.6
    287 
    288 If you've been using !CollabNet's Subversion package, you may need to uninstall that in favor of [https://alagazam.net/ Alagazam], which has the Python bindings readily available, see [trac:TracSubversion]. That package works without tweaking.
    289 
    290 === Changing Database Backend
    291 
    292 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.
    293 
    294 === Upgrading from older versions of Trac #OlderVersions
    295 
    296 For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions].
     261Upgrading Python to a newer version will require reinstallation of Python packages: Trac itself of course, but also [TracInstall#Dependencies dependencies]. If you are using Subversion, you'll need to upgrade the [trac:TracSubversion Python bindings for SVN].
     262
     263
    297264
    298265-----