tower tracking, RT#15538

[freeside.git] / rt / UPGRADING

diff --git a/rt/UPGRADING b/rt/UPGRADING
index 1aaccdb..6466a36 100644 (file)
--- a/rt/UPGRADING
+++ b/rt/UPGRADING
@@ -18,6 +18,48 @@ If you are using MySQL, please read the instructions in UPGRADING.mysql as
 well.
 
 *******
 well.
 
 *******

+UPGRADING FROM 3.8.8 and earlier - Changes:
+
+Previous versions of RT used a password hashing scheme which was too
+easy to reverse, which could allow attackers with read access to the
+RT database to possibly compromise users' passwords.  Even if RT does
+no password authentication itself, it may still store these weak
+password hashes -- using ExternalAuth does not guarantee that you are
+not vulnerable!  To upgrade stored passwords to a stronger hash, run:
+
+    perl etc/upgrade/vulnerable-passwords
+
+
+We've proved that it's possible to delete set of records
+from Transactions table without losing functionality. To delete
+records run the following script:
+
+    perl -I /opt/rt3/local/lib -I /opt/rt3/lib etc/upgrade/shrink_transactions_table.pl
+
+If you chose not to run the shrink_cgm_table.pl script when you upgraded to 3.8,
+you should read more about it below and run it at this point.
+
+UPGRADING FROM 3.8.7 and earlier - Changes:
+
+RT's ChartFont option has been changed from a string to a hash which
+lets you specify per-language fonts. RT now comes with a better default
+font for charts, too.
+
+You should either update your 'ChartFont' option to match the new format
+or consider trying the new default
+
+RT now gives you more precise control over the order in which custom fields
+are displayed.  This change requires some small changes to your currently saved
+custom field orders.
+
+RT will automatically clean up your existing custom fields when you run:
+
+
+  /opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password --action upgrade
+
+After that cleanup, you should make sure that custom fields are ordered in
+a way that you and your users find pleasing.
+

 UPGRADING FROM 3.8.6 and earlier - Changes:
 
 For MySQL and Oracle users:
 UPGRADING FROM 3.8.6 and earlier - Changes:
 
 For MySQL and Oracle users:


@@ -104,10 +146,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
 
 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
 
 
     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
 UPGRADING FROM 3.7.81 and earlier - Changes:
 
 RT::Extension::BrandedQueues has been integrated into core, so you MUST read