[Rt-commit] rt branch, 3.8.9-releng, updated. rt-3.8.8-244-g071d5d9

Kevin Falcone falcone at bestpractical.com
Wed Dec 29 13:29:58 EST 2010


The branch, 3.8.9-releng has been updated
       via  071d5d94c0ad476551c7704709ad4a6a03bb8e0f (commit)
       via  1d061b476ace6b86bd19fc764dba046e6b8385f6 (commit)
      from  5d0d9ceababa754bd3a2278efa35b71568a41938 (commit)

Summary of changes:
 README    |   20 ++++++--------------
 UPGRADING |   11 +++++++++--
 2 files changed, 15 insertions(+), 16 deletions(-)

- Log -----------------------------------------------------------------
commit 1d061b476ace6b86bd19fc764dba046e6b8385f6
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Wed Dec 29 13:29:21 2010 -0500

    a few quick cleanups noticed while I was working on the 4.0 readme

diff --git a/README b/README
index d027837..291a5a5 100644
--- a/README
+++ b/README
@@ -50,11 +50,6 @@ o   Various and sundry perl modules
 GENERAL INSTALLATION
 --------------------
 
-This is a rough guide to installing RT. For more detail, you'll
-want to read a more comprehensive installation guide at:
-
-    http://wiki.bestpractical.com/index.cgi?InstallationGuides
-
 1   Unpack this distribution other than where you want to install RT
 
      To do this cleanly, run the following command:
@@ -72,10 +67,11 @@ want to read a more comprehensive installation guide at:
     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).
+    If you're upgrading RT stop and review the UPGRADING document.
+    Some extensions you're using may have been integrated into
+    core, or there may be other extra steps to follow. It's recommended
+    that you use a 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.
 
@@ -159,9 +155,7 @@ want to read a more comprehensive installation guide at:
 
 8  If you're upgrading from RT 2.0:
 
-    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/
+    Read more in UPGRADING
 
 9   Configure the email and web gateways, as described below.
 
@@ -190,8 +184,6 @@ want to read a more comprehensive installation guide at:
     optional step.
 
 
-
-
 SETTING UP THE WEB INTERFACE
 ----------------------------
 

commit 071d5d94c0ad476551c7704709ad4a6a03bb8e0f
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Wed Dec 29 13:29:29 2010 -0500

    Be more forceful about usage of this script
    
    reported in #13185 that not running it can cause issues

diff --git a/UPGRADING b/UPGRADING
index 8f18073..c69a206 100644
--- a/UPGRADING
+++ b/UPGRADING
@@ -22,7 +22,7 @@ UPGRADING FROM 3.8.8 and earlier - Changes:
 
 We've proved that it's possible to delete set of records
 from Transactions table without losing functionality. To delete
-record run the following script:
+records run the following script:
 
     perl -I /opt/rt3/local/lib -I /opt/rt3/lib etc/upgrade/shrink_transactions_table.pl
 
@@ -133,10 +133,17 @@ UPGRADING FROM 3.7.85 and earlier - Changes:
 
 We've proved that it's possible to delete pretty big set of records
 from CachedGroupMembers table without losing functionality. To delete
-record run the following script:
+record run the following script.  If you don't run this, you may
+occasionally see problems where RT miscounts users, particularly in the
+chart functionality.
 
     perl -I /opt/rt3/local/lib -I /opt/rt3/lib etc/upgrade/shrink_cgm_table.pl
 
+After you run this, you'll have significantly reduced the number of
+records in your CachedGroupMembers table and may need to tell your
+database to refresh indexes/statistics.  Please consult your DBA for
+specific instructions for your database.
+
 UPGRADING FROM 3.7.81 and earlier - Changes:
 
 RT::Extension::BrandedQueues has been integrated into core, so you MUST read

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


More information about the Rt-commit mailing list