[Rt-commit] [rtir] 04/04: Users can't easily test before the RTIR upgrade

[Kevin Falcone]

This is an automated email from the git hooks/post-receive script.

falcone pushed a commit to branch 3.2/siteconfig-cleanups
in repository rtir.

commit fc4e7075742c542eca73520a009aeee77edfbf14
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Fri Aug 29 16:27:30 2014 -0500

    Users can't easily test before the RTIR upgrade
    
    RT blams out if you have a Queue with a lifecycle defined in
    RTIR_Config.pm.  Other things probably also break.  You should ugprade
    RT and RTIR and *then* test.  Testing in the middle is likely to cause
    false alarms.
---
 docs/UPGRADING | 23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/docs/UPGRADING b/docs/UPGRADING
index 554f593..4782720 100644
--- a/docs/UPGRADING
+++ b/docs/UPGRADING
@@ -38,26 +38,20 @@ RTIR 3.0 is not compatible with RT 4.2 releases.
 
 =item 3
 
-Test your upgraded RT. You should be able to start the server,
-log in, use the RT web interface, create tickets, send email to
-RT, receive mail from RT, etc.
-
-=item 4
-
 Make another backup of the DB, so you can return to this step
 if something goes wrong.
 
-=item 5
+=item 4
 
 Install the new version of RTIR. B<DO NOT> run C<make initdb>.
 
-=item 6
+=item 5
 
 Review all of the upgrade notes in docs/UPGRADING-*. If you were
 coming from 2.4.1, you would read UPGRADING-2.4, UPGRADING-2.6 and
-UPGRADING-3.0.
+UPGRADING-3.0 and UPGRADING-3.2.
 
-=item 7
+=item 6
 
 Update RTIR's database.
 
@@ -69,7 +63,7 @@ Answer the prompt for which version of RTIR you are upgrading from. RT
 will then confirm the upgrades that it is going to apply and will run
 them in sequence.
 
-=item 8
+=item 7
 
 Re-analyze and re-optimize your database tables.
 
@@ -77,6 +71,13 @@ When you have completed all of the upgrade steps, you will
 likely need to update any optimizations you have done since the
 underlying tables have probably changed.
 
+=item 8
+
+Test your upgraded RT. You should be able to start the server,
+log in, use the RT web interface, create tickets, send email to
+RT, receive mail from RT, etc.
+
+
 =back
 
 =cut

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.