[Rt-commit] r19908 - rtir/2.5/trunk
ruz at bestpractical.com
ruz at bestpractical.com
Thu Jun 4 19:37:49 EDT 2009
Author: ruz
Date: Thu Jun 4 19:37:49 2009
New Revision: 19908
Modified:
rtir/2.5/trunk/UPGRADING
Log:
* begin filling in UPGRADING
Modified: rtir/2.5/trunk/UPGRADING
==============================================================================
--- rtir/2.5/trunk/UPGRADING (original)
+++ rtir/2.5/trunk/UPGRADING Thu Jun 4 19:37:49 2009
@@ -17,10 +17,13 @@
Also, some files have been renamed and delete, if you leave old
files around, you can hurt functionality of the new version.
- Start from new directory for this installtion instead of using
- directories with previous RT and extensions.
+ If you're upgrading from RTIR 2.4 or newer, so RTIR is already
+ is in local/plugins/RT-IR directory, then you can move it before
+ proceding. Otherwise it's better to start from a new directory
+ for this installtion instead of using directories with previous
+ RT and extensions.
-2) Install and upgrade database to the RT 3.8.1 or newer following
+2) Install and upgrade database to the RT 3.8.4 or newer following
its upgrade instructions.
2.1) Test how RT upgrade went. You should be able to start server,
@@ -29,7 +32,7 @@
2.2) Make another backup of the DB, so you can return to this step
if something goes wrong.
-3) Install or upgrade RTFM 2.4.0rc1 or newer.
+3) Install or upgrade RTFM 2.4.0 or newer.
3.1) Enable it in the RT config using @Plugins option
@@ -75,6 +78,14 @@
--prompt-for-dba-password --action insert \
--datadir etc/upgrade/<version>
+Upgrading from 2.4.x and earlier
+-------------------------
+
+_RTIR_ prefix has been deleted from all RTIR's custom fields. What
+means that you have to update custom code you have: templates,
+scrips and other customizations which may have name of a custom
+field hardcoded.
+
Upgrading from 2.3.17 and earlier
-------------------------
More information about the Rt-commit
mailing list