Changes between Version 99 and Version 100 of TracUpgrade

Timestamp:

Dec 3, 2013, 1:28:42 AM (10 years ago)

Author:

Ryan J Ollos

Comment:

Added suggestion from comment:12:ticket:10825.

TracUpgrade

@@ -79 +79 @@
 ==== Upgrading from Trac 1.0 to 1.1.x ==== #to1.1.x
 
+
+===== New permissions policy for read-only wiki pages
 Since 1.1.2 the read-only attribute of wiki pages is enabled and enforced only when `ReadonlyWikiPolicy` is in the list of active permission policies. If `[trac] permission_policy` has the default value `DefaultPermissionPolicy, LegacyAttachmentPolicy`, then `ReadonlyWikiPolicy` should be automatically appended to the list when upgrading the environment:
 {{{
@@ -90 +92 @@
 ==== Upgrading from Trac 0.12 to Trac 1.0 ==== #to1.0
 
+===== Subversion components not enabled by default for new installations
 The Trac components for Subversion support are no longer enabled by default. To enable the svn support, you need to make sure the `tracopt.versioncontrol.svn` components are enabled, for example by setting the following in the TracIni:
 {{{
@@ -97 +100 @@
 The upgrade procedure should take care of this and change the TracIni appropriately, unless you already had the svn components explicitly disabled.
 
+
+===== Attachments migrated to new location
 Another step in the automatic upgrade will change the way the attachments are stored. If you're a bit paranoid, you might want to take a backup of the `attachments` directory before upgrading (but if you are, you already did a full copy of the environment, no?). 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 go have a look to these files, move them elsewhere and remove the `attachments` directory manually to cleanup the environment. The attachments themselves are now all located in your environment below the `files/attachments` directory.
+
+===== Behavior of `[ticket] default_owner` changed
+Prior 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.