[Rt-commit] rt branch, 4.0-trunk, updated. rt-4.0.0-277-gb4aafe5

[Kevin Falcone]

The branch, 4.0-trunk has been updated
       via  b4aafe53dd1952109088facb92bf824a3a81b128 (commit)
       via  c71c90c692c500435d1af8756ab2d6d8c0efcb18 (commit)
      from  e4e09baca11e8ecf28a4993ef8d5d442d818fb39 (commit)

Summary of changes:
 docs/UPGRADING-4.0 |   27 +++++++++++++++++++++++----
 1 files changed, 23 insertions(+), 4 deletions(-)

- Log -----------------------------------------------------------------
commit c71c90c692c500435d1af8756ab2d6d8c0efcb18
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Wed May 11 12:19:47 2011 -0400

    Make it clearer that upgrading into /opt/rt3 is a terrible idea

diff --git a/docs/UPGRADING-4.0 b/docs/UPGRADING-4.0
index 8a4f02e..9ed5ae8 100644
--- a/docs/UPGRADING-4.0
+++ b/docs/UPGRADING-4.0
@@ -6,12 +6,17 @@ If you are upgrading, you will likely want to specify that your database
 is still named rt3 (or import a backup of your database as rt4 so that
 you can feel more confident making the upgrade).
 
+You really shouldn't install RT4 into your RT3 source tree (/opt/rt3)
+and instead should be using make install to set up a clean environment.
+This will allow you to evaluate your local modifications and configuration
+changes as you migrate to 4.0.
+
 If you choose to force RT to install into /opt/rt3, or another existing RT 3.x
 install location, you will encounter issues because we removed the _Overlay
-files (such as Ticket_Overlay.pm).  You will need to manually remove these
-files after the upgrade or RT will fail.  After making a complete backup of
-your /opt/rt3 install, you might use a command like the following to remove the
-_Overlay files:
+files (such as Ticket_Overlay.pm) and relocated other files.  You will
+need to manually remove these files after the upgrade or RT will fail.
+After making a complete backup of your /opt/rt3 install, you might use a
+command like the following to remove the _Overlay files:
 
     find /opt/rt3/lib/ -type f -name '*_Overlay*' -delete
 

commit b4aafe53dd1952109088facb92bf824a3a81b128
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Wed May 11 12:20:22 2011 -0400

    Talk about upgrading your RT_SiteConfig.pm
    
    Explicitly flag two failure modes we know about

diff --git a/docs/UPGRADING-4.0 b/docs/UPGRADING-4.0
index 9ed5ae8..a930134 100644
--- a/docs/UPGRADING-4.0
+++ b/docs/UPGRADING-4.0
@@ -26,6 +26,18 @@ docs/web_deployment.pod for current instructions.  The old
 work with RT 4.0, and should be removed to reduce confusion.
 
 *******
+RT_SiteConfig.pm
+
+You will need to carefully review your local settings when moving from
+3.8 to 4.0.
+
+If you were adding your own custom statuses in earlier versions of RT,
+using ActiveStatus or InactiveStatus you will need to port these to use
+the new Lifecycles functionality.  You can read more about it in
+RT_Config.pm.  In most cases, you can do this by extending the default
+active and inactive lists.
+
+*******
 Upgrading sessions on MySQL
 
 In 4.0.0rc2, RT began shipping an updated schema for the sesions table
@@ -60,6 +72,8 @@ review this for errors.
 If you are running RTFM 2.0 with a release of RT, there isn't currently an upgrade
 script that can port RTFM's internal CustomField and Transaction data to RT4.
 
+You must also remove RT::FM from your @Plugins line in RT_SiteConfig.pm.
+
 *******
 The deprecated classes RT::Action::Generic, RT::Condition::Generic and RT::Search::Generic
 have been removed, but you shouldn't have been using them anyway. You should have been using

-----------------------------------------------------------------------