[Rt-commit] r17847 - rt/3.999/trunk

[sunnavy at bestpractical.com]

Author: sunnavy
Date: Wed Jan 21 00:58:25 2009
New Revision: 17847

Modified:
   rt/3.999/trunk/   (props changed)
   rt/3.999/trunk/README

Log:
 r18933 at sunnavys-mb:  sunnavy | 2009-01-21 10:31:00 +0800
 started to merge from 13314@ to 3.8.2, i.e. 17598@


Modified: rt/3.999/trunk/README
==============================================================================
--- rt/3.999/trunk/README	(original)
+++ rt/3.999/trunk/README	Wed Jan 21 00:58:25 2009
@@ -21,8 +21,7 @@
 o   Perl 5.8.3 or later (http://www.perl.com).
 
        Perl versions prior to 5.8.3 contain bugs that could result
-       in data corruption. We recommend strongly that you use 5.8.3
-       or newer.
+       in data corruption. RT won't start on older versions.
 
 o   A supported SQL database
 
@@ -33,12 +32,8 @@
 
 o   Apache version 1.3.x or 2.x (http://httpd.apache.org) 
         with mod_perl -- (http://perl.apache.org ) 
-        or a webserver with FastCGI support (www.fastcgi.com)
-
-        Compiling mod_perl on Apache 1.3.x as a DSO has been known 
-        to have massive stability problems and is not recommended.
-
-        mod_perl 1.x must be built with EVERYTHING=1
+        or with FastCGI -- (www.fastcgi.com)
+        or other webserver with FastCGI support
 
         RT's FastCGI handler needs to access RT's configuration file.
 
@@ -77,6 +72,11 @@
     default install directory in /opt/rt3 does not work under SELinux's
     default configuration.
 
+    If you're upgrading RT then it worth to read UPGRADING document at this
+    moment. Some extension you're using may have been integrated into
+    core. It's recommended to use new clean directory when you're
+    upgrading to new major release (for example from 3.6.x to 3.8.x).
+
 3   Make sure that RT has everything it needs to run.
 
     Check for missing dependencies by running:
@@ -121,8 +121,9 @@
 
 7   If you're upgrading from RT 3.0 or newer:
 
-     Read through the UPGRADING document included in this distribution.
-     
+     Read through the UPGRADING document included in this distribution. If
+     you're using MySQL, read through UPGRADING.mysql as well.
+
      It includes special upgrade instructions that will help you get this
      new version of RT up and running smoothly.
 
@@ -138,19 +139,16 @@
      You'll need to add any new values you need to change from the defaults 
      in etc/RT_Config.pm
 
-     You may also need to update RT's database.  To find out, type:
+     You may also need to update RT's database.  You can do this with 
+     the rt-setup-database tool.  Replace root with the name of the dba
+     user on your database (root is the default for MySQL).
 
-       ls etc/upgrade
+     You will be prompted for your previous version of RT (such as 3.6.4)
+     so that we can calculate which database updates to apply
 
-     For each item in that directory whose name is greater than
-     your previously installed RT version, run:
+     You should back up your database before running this command.
 
-       /opt/rt3/sbin/rt-setup-database --action schema \
-           --datadir etc/upgrade/<version>
-       /opt/rt3/sbin/rt-setup-database --action acl \
-           --datadir etc/upgrade/<version>
-       /opt/rt3/sbin/rt-setup-database --action insert \
-            --datadir etc/upgrade/<version>
+       /opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password --action upgrade
 
      Clear mason cache dir:
 
@@ -161,8 +159,9 @@
 
 8  If you're upgrading from RT 2.0:
 
-    Please upgrade from RT 2.0 to RT 3.2 and then follow the instructions
-    for section 7.
+    Use the RT::Extension::RT2toRT3 module to upgrade to the current RT
+    release.  You can download it from CPAN here:
+    http://search.cpan.org/dist/RT-Extension-RT2toRT3/
 
 9   Configure the email and web gateways, as described below.