[Rt-commit] rt branch, 4.0/upgrading-docs, updated. rt-4.0.0rc6-43-gf990c0c

[Alex Vandiver]

The branch, 4.0/upgrading-docs has been updated
       via  f990c0c66464c989dd7a12f8bcfbd2c542ca6fee (commit)
      from  af8ae55ef8bbf0e66b52950e4b6b010a5cfb8ae3 (commit)

Summary of changes:
 docs/UPGRADING-3.2 |    8 ++++--
 docs/UPGRADING-3.4 |   13 +++++------
 docs/UPGRADING-3.6 |   56 ++++++++++++++++++++++++++++-----------------------
 3 files changed, 42 insertions(+), 35 deletions(-)

- Log -----------------------------------------------------------------
commit f990c0c66464c989dd7a12f8bcfbd2c542ca6fee
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Wed Mar 16 13:46:53 2011 -0700

    More rewording and rewrapping in upgrade docs

diff --git a/docs/UPGRADING-3.2 b/docs/UPGRADING-3.2
index 9510814..c0b8ceb 100644
--- a/docs/UPGRADING-3.2
+++ b/docs/UPGRADING-3.2
@@ -2,8 +2,10 @@ UPGRADING FROM 3.2 and earlier - Changes:
 
 = Rights changes =
 
-Now, if you want any user to be able to access the Admin tools (a.k.a. 
-the Configuration tab), you must grant that user the "ShowConfigTab" 
+Now, if you want any user to be able to access the Admin tools (a.k.a.
+the Configuration tab), you must grant that user the "ShowConfigTab"
 right.  Making the user a privileged user is no longer sufficient.
 
-"SuperUser" users are no longer automatically added to the list of users who can own tickets in a queue. You now need to explicitly give them the "own tickets" right.
+"SuperUser" users are no longer automatically added to the list of users
+who can own tickets in a queue. You now need to explicitly give them the
+"OwnTicket" right.
diff --git a/docs/UPGRADING-3.4 b/docs/UPGRADING-3.4
index 5e5ca7b..4dca045 100644
--- a/docs/UPGRADING-3.4
+++ b/docs/UPGRADING-3.4
@@ -1,13 +1,12 @@
 UPGRADING FROM 3.3.14 and earlier - Changes:
 
-The "ModifyObjectCustomFieldValues" right name was too long. It's been changed to
-"ModifyCustomField"
+The "ModifyObjectCustomFieldValues" right name was too long. It has been
+changed to "ModifyCustomField"
 
 
 UPGRADING FROM 3.3.11 and earlier - Changes:
 
-= Rights Changes =
-
-Custom Fields now have an additional right "ModifyCustomField". 
-This right governs whether a user can modify an object's custom field values
-for a particular custom field. This includes adding, deleting and changing values.
+Custom Fields now have an additional right, "ModifyCustomField".  This
+right governs whether a user can modify an object's custom field values
+for a particular custom field. This includes adding, deleting and
+changing values.
diff --git a/docs/UPGRADING-3.6 b/docs/UPGRADING-3.6
index 15c7346..d0883a9 100644
--- a/docs/UPGRADING-3.6
+++ b/docs/UPGRADING-3.6
@@ -1,43 +1,49 @@
 UPGRADING FROM 3.6.X and earlier - Changes:
 
-There are a lot of changes all over the code, so it's highly recommended to
-use fresh directory and then reinstalling your customizations.
+As there are a large number of code changes, it is highly recommended
+that you install RT into a fresh directory, and then reinstall your
+customizations.
 
-New schema for mysql 4.1 and greater, read more in UPGRADING.mysql.
+The database schema has changed significantly for mysql 4.1 and above;
+please read UPGRADING.mysql for more details.
 
-Config format has been made stricter. All options MUST be set using Set
-function, no more "@XXX = (...) unless @XXX;". Use "Set(@XXX, ...);" instead.
+The configuration format has been made stricter. All options MUST be set
+using the Set function; the historical "@XXX = (...) unless @XXX;" is no
+longer allowed.
 
-RTx::Shredder extension has been integrated into core and features have been
-added, so you MUST uninstall it before upgrading or use a fresh directory for
-installation.
+The RTx::Shredder extension has been integrated into core, and several
+features have been added, so you MUST uninstall it before upgrading.
 
-New interface for making links in text clickable and doing other replacements
-has been integrated into RT.
-Read more in `perldoc docs/extending_clickable_links.pod`.
+A new interface for making links in text clickable, and doing other
+arbitrary text replacements, has been integrated into RT.  You can read
+more in `perldoc docs/extending_clickable_links.pod`.
 
-New feature that allow users to forward messages. There is a new option in
-the config ($ForwardFromUser), new rights and a template.
+A new feature has been added that allows users to forward
+messages. There is a new option in the config ($ForwardFromUser), new
+rights, and a new template.
 
-New global templates with "Error: " prefix in the name to make it possible
-to configure error messages sent to users.
+New global templates have been added with "Error: " prefixed to the name
+to make it possible to configure error messages sent to users.
 
-Read about GnuPG integration in `perldoc docs/gnupg_integration.pod`.
+You can read about the new GnuPG integration in `perldoc
+lib/RT/Crypt/GnuPG.pm`.
+
+New scrip conditions 'On Close' and 'On Reopen' have been added.
 
-New scrip conditions 'On Close' and 'On Reopen'.
 
 UPGRADING FROM 3.5.7 and earlier - Changes:
 
-Scrips are now prepared and committed in order alphanumerically by description.
-This means that you can prepend a number (00, 07, 15, 24) to the beginning of
-each scrip's description, and they will run in that order.  Depending on your
-database, the old ordering may have been by scrip id number -- if that is the
-case, simply prepend the scrip id number to the beginning of its description.
+Scrips are now prepared and committed in order alphanumerically by
+description.  This means that you can prepend a number (00, 07, 15, 24)
+to the beginning of each scrip's description, and they will run in that
+order.  Depending on your database, the old ordering may have been by
+scrip id number -- if that is the case, simply prepend the scrip id
+number to the beginning of its description.
 
 
 UPGRADING FROM 3.5.1 and earlier - Changes:
 
 The default for $RedistributeAutoGeneratedMessages has changed to
-'privileged', to make out-of-the-box installations more resistant
-to mail loops. If you rely on the old default of redistributing to
-all watchers, you'll need to set it explicitly now.
+'privileged', to make out-of-the-box installations more resistant to
+mail loops. If you rely on the old default of redistributing to all
+watchers, you'll need to set it explicitly now.

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