Changes between Version 47 and Version 48 of TracUpgrade

Timestamp:

Dec 7, 2007, 9:12:11 PM (16 years ago)

Author:

Christian Boos

Comment:

Fix small errors and adapt content to the new toplevel location

TracUpgrade

@@ -2 +2 @@
 [[TracGuideToc]]
 
-A [wiki:TracEnvironment Trac environment] needs to be upgraded before it can be used with Trac-0.11. This document describes the steps necessary to upgrade an environment.
+A [TracEnvironment Trac environment] needs to be upgraded before it can be used with Trac 0.11. This document describes the steps necessary to upgrade an environment.
 
- '''Note''': ''Environment upgrades are not necessary for minor version releases unless otherwise noted. 
+Environment upgrades are not necessary for minor version releases unless otherwise noted. 
 
- '''Note''': ''A database change is required, so it is no longer safe to switch back from 0.11 to 0.10.
-
- '''Beware:''' milestone:0.11 still says it is safe to switch between 0.10.4 and 0.11dev
 
 == Instructions ==
@@ -16 +13 @@
 === Update the Trac Code ===
 
-Get the new version as described in wiki:0.11/TracInstall, or your operation system specific procedure.
+Get the new version as described in TracInstall, or your operation system specific procedure.
 
 If you do a manual (not operating system specific) upgrade, you may also later on want to remove the existing Trac code by deleting the `trac` directory from the Python `lib/site-packages` directory.
@@ -27 +24 @@
 You may also want to remove the Trac `cgi-bin`, `htdocs`, `templates` and `wiki-default` directories that are commonly found in a directory called `share/trac` (the exact location depends on your platform).
 
-> If You had the webadmin components, You should disable (remove from config file) webadmin.* -  now Admin is part of the Trac code base.
-
+> If you had the webadmin plugin installed, you can now uninstall it as it is now part of the Trac code base.
 
 
 === Upgrade the Trac Environment ===
 
-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 [wiki:TracAdmin trac-admin]:
+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]:
 {{{
 trac-admin /path/to/projenv upgrade
@@ -47 +43 @@
 === Update the Trac Documentation ===
 
-Every [wiki:TracEnvironment Trac environment] includes a copy of the Trac documentation for the installed version. As you probably want to keep the included documentation in sync with the installed version of Trac, [wiki:TracAdmin trac-admin] provides a command to upgrade the documentation:
+Every [TracEnvironment Trac environment] includes a copy of the Trac documentation for the installed version. As you probably want to keep the included documentation in sync with the installed version of Trac, [TracAdmin trac-admin] provides a command to upgrade the documentation:
 {{{
 trac-admin /path/to/projenv wiki upgrade
@@ -55 +51 @@
 
 === 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 ClearSilver and the HDF); they need to be converted to the new-style macros.
+The Trac macros will need to be adapted, as the old-style wiki-macros are not supported anymore (due to the drop of ClearSilver and the HDF); they need to be converted to the new-style macros, see TracWikiMacros.
 
 
@@ -63 +59 @@
 == Known Issues ==
 === parent dir ===
-If you use a trac parent env configuration and one of the plugines in one child does not work, none of the children work.
+If you use a trac parent env configuration and one of the plugins in one child does not work, none of the children work.
 
 == Changing Database Backend ==
@@ -72 +68 @@
 == Older Versions ==
 
-For upgrades from former versions refer to TracUpgrade.
+For upgrades from former versions refer to wiki:0.10/TracUpgrade.
 
 -----