[Rt-commit] rt branch, 5.0/recommend-fresh-install, created. rt-5.0.0alpha1-7-g181768804

Jim Brandt jbrandt at bestpractical.com
Tue Feb 25 09:16:40 EST 2020


The branch, 5.0/recommend-fresh-install has been created
        at  18176880421746a155a9c36b7ac83cd473e0bbc1 (commit)

- Log -----------------------------------------------------------------
commit 14ea72ae489711f5a89bd44ccc8def3c5ceefea9
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Tue Feb 25 09:14:44 2020 -0500

    Recommend installing into a fresh /opt/rt5 directory
    
    Many early bug reports are from upgrading over an
    existing /opt/rt4 because many files have been moved
    and we don't delete files on upgrade.

diff --git a/docs/UPGRADING-5.0 b/docs/UPGRADING-5.0
index 84cb026ec..1df657a75 100644
--- a/docs/UPGRADING-5.0
+++ b/docs/UPGRADING-5.0
@@ -10,6 +10,32 @@ before you upgrade and look for changes to features you currently use.
 See F<devel/docs/UPGRADING-5.0> for internals changes relevant to
 extension writers, including deprecated code.
 
+=head2 Upgrading Recommendations
+
+RT now defaults to a database name of rt5 and an installation root of
+/opt/rt5.
+
+If you are upgrading, you will likely want to specify that your database is
+still named rt4 or even rt3. Alternatively, you could import a backup of your
+database as rt5 to conform to the new default, although this isn't required.
+
+Upgrading to RT 5 over an existing RT 4 installation (/opt/rt4) is not
+recommended and will almost certainly cause issues. Instead, do a fresh
+install into /opt/rt5 (or your custom location) for the code portion of the
+upgrade. Then import your existing database and run the database upgrade
+steps using make upgrade-database.
+
+We recommend this approach because of the large number of changes to the code
+base for this major release. We moved some things to new locations and old
+files are not removed as part of the upgrade process. These old files will
+still be detected by RT in some cases and will cause issues.
+
+Installing a fresh code base will also allow you to evaluate your local
+modifications and configuration changes as you migrate to 5.0. If you have
+changes made directly to the RT code, it's a good time to look at the hooks
+RT provides for custom code in extensions or in the local directory. See
+F<docs/writing_extensions.pod> for more information.
+
 =over
 
 =item *

commit 18176880421746a155a9c36b7ac83cd473e0bbc1
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Tue Feb 25 09:16:25 2020 -0500

    Clarify notes on when Articles was added to core

diff --git a/docs/UPGRADING-4.0 b/docs/UPGRADING-4.0
index e19bb4f7b..04a02a927 100644
--- a/docs/UPGRADING-4.0
+++ b/docs/UPGRADING-4.0
@@ -12,7 +12,7 @@ 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 rt5 so that you can
 feel more confident making the upgrade).
 
-You really shouldn't install RT5 into your RT3 source tree (/opt/rt3) and
+You really shouldn't install RT 5 into your RT 3 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 or 5.0.
@@ -62,17 +62,18 @@ the new schema.
 
 =head2 Upgrading from installs with RTFM
 
-RT5 now includes an Articles functionality, merged from RTFM.  You should not
-install and enable the RT::FM plugin separately on RT 4.  If you have existing
-data in RTFM, you can use the /opt/rt5/etc/upgrade/upgrade-articles script to upgrade
+Starting with version 4, RT includes a Articles functionality, merged from RTFM.
+You should not install and enable the RT::FM plugin separately on RT 4.
+If you have existing data in RTFM, you can use the
+C</opt/rt5/etc/upgrade/upgrade-articles> script to upgrade
 that data.
 
 When running normal upgrade scripts, RT will warn if it finds existing RTFM
 tables that contain data and point you to the upgrade-articles script.
 
 This script should be run from your RT tarball.  It will immediately begin
-populating your new RT5 tables with data from RTFM.  If you have browsed in
-the RT5 UI and created new classes and articles, this script will fail
+populating your new RT 5 tables with data from RTFM.  If you have browsed in
+the RT 5 UI and created new classes and articles, this script will fail
 spectacularly.  Do *not* run this except on a fresh upgrade of RT.
 
 You can run this as

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


More information about the rt-commit mailing list