Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Request Tracker: Commit

rt branch, 4.2/convert-upgrading-4.2-to-pod, repushed

 

 

Request Tracker commit RSS feed   Index | Next | Previous | View Threaded


jbrandt at bestpractical

Aug 7, 2013, 6:46 AM

Post #1 of 2 (15 views)
Permalink
rt branch, 4.2/convert-upgrading-4.2-to-pod, repushed

The branch 4.2/convert-upgrading-4.2-to-pod was deleted and repushed:
was 45dbc9e2f9a1e2c7de26e1167fdfc7a36afc0c3a
now aafd79758e5ce87cd6bb6139782a03c16bf522de

1: 45dbc9e ! 1: 4cae93f Convert UPGRADING-4.2 to POD
@@ -93,13 +93,6 @@
- command:
+=head1 UPGRADING FROM RT 4.0.0 and greater
+
-+The 4.2 release is a major upgrade and as such there are more changes
-+than in a minor bugfix release (e.g., 4.0.13 to 4.0.14). The following
-+lists some of the notable changes, especially those that might require
-+you to change a configuration option or other setting due to a change
-+in RT. Read this section carefully before you upgrade and look for
-+changes to features you currently use.
-+
+=over
+
+=item *
@@ -112,7 +105,8 @@
+
+=item *
+
-+The L<RT_Config/$LogToScreen> config setting is now named C<$LogToSTDERR> which
++The C<$LogToScreen> config setting is now named
++L<< "C<$LogToSTDERR>"|RT_Config/"$LogToSyslog, $LogToSTDERR" >> which
+better describes what the log level controls. Setting C<$LogToScreen> will
+still work, but an informational notice will be issued on server start telling
+you about the rename. To avoid this you should set C<$LogToSTDERR> instead.
@@ -140,7 +134,7 @@
+=item *
+
+MakeClicky handlers added via a callback are now passed an "object" key in
-+the parameter hash instead of "ticket". The object may be any C<RT::Record>
++the parameter hash instead of "ticket". The object may be any L<RT::Record>
+subclass.
+
+=item *
@@ -183,7 +177,7 @@
+
+=item *
+
-+The C<@JSFiles> config now only keeps additional JavaScript filenames; if
++The L<RT_Config/@JSFiles> config now only keeps additional JavaScript filenames; if
+you had copied C<@JSFiles> to add extra entries in your C<RT_SiteConfig.pm>,
+remove the core JS from the list, or RT will serve those files
+multiple times.
@@ -208,14 +202,14 @@
+The C<Googleish> search has been renamed to C<Simple>. If you were
+using this in an L<< C<rt-crontool> >> cronjob or had used a
+C<Googleish_Local.pm> to add features, you will need to convert to
-+using C<RT::Search::Simple> instead.
++using L<RT::Search::Simple> instead.
+
+=item *
+
+RT was recording additional time change transactions during merge, so
+the time difference in a ticket's history doesn't add up to the value on
+the ticket. This has been fixed. Time is adjusted during merge, but now
-+transactions are recorded.
++transactions are not recorded.
+
+In order to fix the history records of old ticket you can run the following
+command:
@@ -262,10 +256,11 @@
+
+CSS is no longer processed through Mason; it's served by a proper static file
+handler. If you used the C<Begin> or C<End> callbacks of C<main.css> in the
-+aileron, web2, or ballard themes, you should transition to the C<@CSSFiles>
-+config option. If you need to target specific themes, you can use the class
-+set on the E<lt>C<body>E<gt> element (for example: body.aileron). See
-+F<docs/customizing/styling_rt.pod> for more information on custom styles.
++aileron, web2, or ballard themes, you should transition to the
++L<RT_Config/@CSSFiles> config option. If you need to target specific themes,
++you can use the class set on the E<lt>C<body>E<gt> element (for example:
++body.aileron). See F<docs/customizing/styling_rt.pod> for more information
++on custom styles.
+
+=item *
+
@@ -312,6 +307,23 @@
-* 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:
+-
+- Set($WebSessionClass, "Apache::Session::File");
+-
+-* Configuration options dealing with "external authentication" have been
+- renamed to reduce confusion with the common extension
+- RT::Authen::ExternalAuth. The old names will work, but produce
+- deprecation warnings. The old names, and their new counterparts, are:
+-
+- WebExternalAuth => WebRemoteUserAuth
+- WebExternalAuthContinuous => WebRemoteUserContinuous
+- WebFallbackToInternalAuth => WebFallbackToRTLogin
+- WebExternalGecos => WebRemoteUserGecos
+- WebExternalAuto => WebRemoteUserAutocreate
+- AutoCreate => UserAutocreateDefaultsOnLogin
+-
+-* Due to many long-standing bugs and limitations, the "Offline Tool" was
+- removed.
+=item *
+
+The Articles menu is now a top-level menu item and display is controlled by
@@ -352,15 +364,9 @@
+=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 the
-+following is in your C<RT_SiteConfig.pm>:
-
- Set($WebSessionClass, "Apache::Session::File");
-
--* Configuration options dealing with "external authentication" have been
-- renamed to reduce confusion with the common extension
-- RT::Authen::ExternalAuth. The old names will work, but produce
-- deprecation warnings. The old names, and their new counterparts, are:
++on-disk. If you wish to preserve the original behavior, ensure that
++L<RT_Config/$WebSessionClass> is set in your C<RT_SiteConfig.pm>.
++
+=item *
+
+Configuration options dealing with "external authentication" have been
@@ -379,15 +385,8 @@
+
+Due to many long-standing bugs and limitations, the "Offline Tool" was
+removed.
-
-- WebExternalAuth => WebRemoteUserAuth
-- WebExternalAuthContinuous => WebRemoteUserContinuous
-- WebFallbackToInternalAuth => WebFallbackToRTLogin
-- WebExternalGecos => WebRemoteUserGecos
-- WebExternalAuto => WebRemoteUserAutocreate
-- AutoCreate => UserAutocreateDefaultsOnLogin
++
+=back
-
--* Due to many long-standing bugs and limitations, the "Offline Tool" was
-- removed.
++
+=cut
+
-: ------- > 2: aafd797 Add intro text to UPGRADING-4.2 doc

_______________________________________________
Rt-commit mailing list
Rt-commit [at] lists
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-commit


jbrandt at bestpractical

Aug 8, 2013, 6:14 AM

Post #2 of 2 (12 views)
Permalink
rt branch, 4.2/convert-upgrading-4.2-to-pod, repushed [In reply to]

The branch 4.2/convert-upgrading-4.2-to-pod was deleted and repushed:
was aafd79758e5ce87cd6bb6139782a03c16bf522de
now 88c44a64dc0e2e1bc716b479dc71666498738d4b

1: 4cae93f ! 1: 24483b5 Convert UPGRADING-4.2 to POD
@@ -206,10 +206,13 @@
+
+=item *
+
-+RT was recording additional time change transactions during merge, so
-+the time difference in a ticket's history doesn't add up to the value on
-+the ticket. This has been fixed. Time is adjusted during merge, but now
-+transactions are not recorded.
++On merge, RT retains transactions from both tickets. Previously, RT
++also recorded explicit time change transactions during a
++merge to adjust the total time spent. This caused the total time
++spent, as summed from transactions, to be different from the ticket's
++overall time spent. This has been fixed: time is adjusted during the
++merge commit itself, removing the need for the confusing
++extra transactions, and keeping the summed time spent consistent.
+
+In order to fix the history records of old ticket you can run the following
+command:
@@ -307,86 +310,83 @@
-* 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:
--
-- Set($WebSessionClass, "Apache::Session::File");
--
++=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 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, the actions are available from the admin scrip pages.
++
++=item *
++
++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");
+
-* Configuration options dealing with "external authentication" have been
- renamed to reduce confusion with the common extension
- RT::Authen::ExternalAuth. The old names will work, but produce
- deprecation warnings. The old names, and their new counterparts, are:
--
++=item *
++
++Configuration options dealing with "external authentication" have been
++renamed to reduce confusion with the common extension
++L<RT::Authen::ExternalAuth>. The old names will work, but produce
++deprecation warnings. The old names, and their new counterparts, are:
++
++ WebExternalAuth => WebRemoteUserAuth
++ WebExternalAuthContinuous => WebRemoteUserContinuous
++ WebFallbackToInternalAuth => WebFallbackToRTLogin
++ WebExternalGecos => WebRemoteUserGecos
++ WebExternalAuto => WebRemoteUserAutocreate
++ AutoCreate => UserAutocreateDefaultsOnLogin
++
++=item *
++
++Due to many long-standing bugs and limitations, the "Offline Tool" was
++removed.
+
- WebExternalAuth => WebRemoteUserAuth
- WebExternalAuthContinuous => WebRemoteUserContinuous
- WebFallbackToInternalAuth => WebFallbackToRTLogin
- WebExternalGecos => WebRemoteUserGecos
- WebExternalAuto => WebRemoteUserAutocreate
- AutoCreate => UserAutocreateDefaultsOnLogin
--
++=back
+
-* Due to many long-standing bugs and limitations, the "Offline Tool" was
- removed.
-+=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 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, the actions are available from the admin scrip pages.
-+
-+=item *
-+
-+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>.
-+
-+=item *
-+
-+Configuration options dealing with "external authentication" have been
-+renamed to reduce confusion with the common extension
-+L<RT::Authen::ExternalAuth>. The old names will work, but produce
-+deprecation warnings. The old names, and their new counterparts, are:
-+
-+ WebExternalAuth => WebRemoteUserAuth
-+ WebExternalAuthContinuous => WebRemoteUserContinuous
-+ WebFallbackToInternalAuth => WebFallbackToRTLogin
-+ WebExternalGecos => WebRemoteUserGecos
-+ WebExternalAuto => WebRemoteUserAutocreate
-+ AutoCreate => UserAutocreateDefaultsOnLogin
-+
-+=item *
-+
-+Due to many long-standing bugs and limitations, the "Offline Tool" was
-+removed.
-+
-+=back
-+
+=cut

2: aafd797 = 2: 88c44a6 Add intro text to UPGRADING-4.2 doc

_______________________________________________
Rt-commit mailing list
Rt-commit [at] lists
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-commit

Request Tracker commit RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.