[Rt-commit] rt branch, master, updated. rt-4.1.19-15-g96318fe

[Alex Vandiver]

The branch, master has been updated
       via  96318fed518f9ca3d1f153b1a79f346cf9d48e87 (commit)
       via  88c44a64dc0e2e1bc716b479dc71666498738d4b (commit)
       via  24483b59cfd0d50c043e385ba5770dd091be8da3 (commit)
      from  1dd4dbf45aa16e4ca10a706e5a8caffe6aaeebb9 (commit)

Summary of changes:
 docs/UPGRADING-4.2 | 404 +++++++++++++++++++++++++++++++----------------------
 1 file changed, 239 insertions(+), 165 deletions(-)

- Log -----------------------------------------------------------------
commit 96318fed518f9ca3d1f153b1a79f346cf9d48e87
Merge: 1dd4dbf 88c44a6
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Tue Aug 20 15:35:15 2013 -0400

    Merge branch '4.2/convert-upgrading-4.2-to-pod'
    
    Conflicts:
    	docs/UPGRADING-4.2
    
    Updated for changes in 54d485c

diff --cc docs/UPGRADING-4.2
index a2cf0a0,ef9d2a8..b7e2015
--- a/docs/UPGRADING-4.2
+++ b/docs/UPGRADING-4.2
@@@ -116,63 -170,48 +170,75 @@@ To switch from HTML back to text, run
  
      /opt/rt4/etc/upgrade/switch-templates-to text
  
- * The Articles menu is now a top-level menu item and display is controlled by
-   the right ShowArticlesMenu.  This right is only grantable globally to groups
-   or users.  During the upgrade, the new right will be automatically granted to
-   Privileged users so that the menu doesn't disappear for anyone previously
-   using it.  You may wish to revoke the right from Privileged and grant it
-   more selectively.
+ =item *
+ 
+ The Articles menu is now a top-level menu item and display is controlled by
+ the right C<ShowArticlesMenu>.  This right is only grantable globally to groups
+ or users.  During the upgrade, the new right will be automatically granted to
+ Privileged users so that the menu doesn't disappear for anyone previously
+ using it.  You may wish to revoke the right from Privileged and grant it
+ more selectively.
+ 
+ =item *
+ 
+ The Owner drop-down now only includes privileged users (no matter if
+ unprivileged users have been granted the OwnTicket right) because
+ configurations which have unprivileged Owners are exceedingly rare,
+ and granting Everyone the OwnTicket right is a common cause of
+ performance problems.  Unprivileged Owners (if they exist) may still
+ be set using the Autocompleter.
+ 
+ =item *
  
- * The Owner drop-down now only includes privileged users (no matter if
-   unprivileged users have been granted the OwnTicket right) because
-   configurations which have unprivileged Owners are exceedingly rare,
-   and granting Everyone the OwnTicket right is a common cause of
-   performance problems.  Unprivileged Owners (if they exist) may still
-   be set using the Autocompleter.
+ The functionality that changed the ticket status to Open when the Started
+ date is set has been moved to a Scrip called 'On transaction and SetStarted
+ Open Ticket'. If you do not depend on this functionality, the Scrip can
+ be deleted.
  
- * The functionality that changed the ticket status to Open when the Started
-   date is set has been moved to a Scrip called 'On transaction and SetStarted
-   Open Ticket'. If you do not depend on this functionality, the Scrip can
-   be deleted.
+ =item *
  
- * New installs will notify Ccs and one-time Ccs/Bccs on create and Owners on
-   create and correspond.  Upgraded installations will not.  If you'd like to
-   adjust your scrips to match the new install behavior, create and edit the
-   following scrips from the admin scrip page:
+ New installs will notify Ccs and one-time Ccs/Bccs on create and Owners on
+ create and correspond.  Upgraded installations will not.  If you'd like to
 -adjust your scrips, the actions are available from the admin scrip pages.
++adjust your scrips to match the new install behavior, create and edit the
++following scrips from the admin scrip page:
 +
-   To notify Ccs on create, on the 'Create a global scrip' page:
++To notify Ccs on create, on the 'Create a global scrip' page:
 +
-     Description: On Create Notify Ccs
-     Condition:   On Create
-     Action:      Notify Ccs
-     Template:    Correspondence in HTML
++  Description: On Create Notify Ccs
++  Condition:   On Create
++  Action:      Notify Ccs
++  Template:    Correspondence in HTML
 +
-   To notify one-time Ccs/Bccs on create, on the 'Create a global scrip' page:
++To notify one-time Ccs/Bccs on create, on the 'Create a global scrip' page:
 +
-     Description: On Create Notify Other Recipients
-     Condition:   On Create
-     Action:      Notify Other Recipients
-     Template:    Correspondence in HTML
++  Description: On Create Notify Other Recipients
++  Condition:   On Create
++  Action:      Notify Other Recipients
++  Template:    Correspondence in HTML
 +
-   To notify Owners on create, click 'On Create Notify AdminCcs'. Change the
-   fields listed below to their corresponding values:
++To notify Owners on create, click 'On Create Notify AdminCcs'. Change the
++fields listed below to their corresponding values:
 +
-     Description: On Create Notify Owner and AdminCcs
-     Action:      Notify Owner and AdminCcs
++  Description: On Create Notify Owner and AdminCcs
++  Action:      Notify Owner and AdminCcs
 +
-   To notify Owners on correspond, click 'On Correspond Notify AdminCcs'. Change
-   the fields listed below to their corresponding values:
++To notify Owners on correspond, click 'On Correspond Notify AdminCcs'. Change
++the fields listed below to their corresponding values:
 +
-     Description: On Correspond Notify Owner and AdminCcs
-     Action:      Notify Owner and AdminCcs
++  Description: On Correspond Notify Owner and AdminCcs
++  Action:      Notify Owner and AdminCcs
  
- * Notifications to AdminCcs on approvals are now handled via the New Pending
-   Approval template in the hidden ___Approvals queue.  If you customized the
-   Transaction template, you should port your changes to New Pending Approval.
+ =item *
  
- * On Oracle, sessions are now stored in the database by default instead of
-   on-disk.  If you wish to preserve the original behaviour, ensure the
-   following is in your RT_SiteConfig.pm:
+ Notifications to AdminCcs on approvals are now handled via the New Pending
+ Approval template in the hidden ___Approvals queue.  If you customized the
+ Transaction template, you should port your changes to New Pending Approval.
+ 
+ =item *
+ 
+ On Oracle, sessions are now stored in the database by default instead of
+ on-disk.  If you wish to preserve the original behavior, ensure that
+ L<RT_Config/$WebSessionClass> is set in your C<RT_SiteConfig.pm>:
  
      Set($WebSessionClass, "Apache::Session::File");
  

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