[Rt-commit] rt branch, master, updated. rt-4.2.12-444-g5cde719
Shawn Moore
shawn at bestpractical.com
Mon Nov 2 10:43:08 EST 2015
The branch, master has been updated
via 5cde719f734b3b0c816b5910d86f417839a8049f (commit)
from 97f6582ce5cfc910374dfa92afd461451ec1bebf (commit)
Summary of changes:
README | 10 +++++-----
docs/customizing/styling_rt.pod | 2 +-
docs/extensions.pod | 6 +++---
docs/writing_extensions.pod | 2 +-
4 files changed, 10 insertions(+), 10 deletions(-)
- Log -----------------------------------------------------------------
commit 5cde719f734b3b0c816b5910d86f417839a8049f
Author: Shawn M Moore <shawn at bestpractical.com>
Date: Mon Nov 2 10:41:49 2015 -0500
Update various references to version numbers in the docs
diff --git a/README b/README
index 4163ba4..5910316 100644
--- a/README
+++ b/README
@@ -66,10 +66,10 @@ GENERAL INSTALLATION
If you are upgrading from a previous version of RT, please review
the upgrade notes for the appropriate versions, which can be found
- in docs/UPGRADING-* If you are coming from 4.0.x to 4.2.x you should
- review both the UPGRADING-4.0 and UPGRADING-4.2 files. Similarly, if
- you were coming from 3.8.x, you would want to review the UPGRADING-3.8,
- UPGRADING-4.0 and UPGRADING-4.2 documents.
+ in docs/UPGRADING-* If you are coming from 4.2.x to 4.4.x you should
+ review both the UPGRADING-4.2 and UPGRADING-4.4 files. Similarly, if
+ you were coming from 4.0.x, you would want to review the UPGRADING-4.0,
+ UPGRADING-4.2 and UPGRADING-4.4 documents.
Any upgrade steps given in version-specific UPGRADING files should
be run after the rest of the steps below; however, please read the
@@ -159,7 +159,7 @@ GENERAL INSTALLATION
You should back up your database before running this command.
When you run it, you will be prompted for your previous version of
- RT (such as 4.0.23) so that the appropriate set of database
+ RT (such as 4.2.12) so that the appropriate set of database
upgrades can be applied.
If 'make upgrade-database' completes without error, your upgrade
diff --git a/docs/customizing/styling_rt.pod b/docs/customizing/styling_rt.pod
index 7e37d00..a744bb0 100644
--- a/docs/customizing/styling_rt.pod
+++ b/docs/customizing/styling_rt.pod
@@ -18,7 +18,7 @@ RT comes with the following themes:
=item rudder
-The default layout for RT 4.2
+The default layout for RT 4.2 and 4.4
=item aileron
diff --git a/docs/extensions.pod b/docs/extensions.pod
index 502e37f..0dde5f8 100644
--- a/docs/extensions.pod
+++ b/docs/extensions.pod
@@ -52,9 +52,9 @@ documentation.
=item 5.
-B<Add the plugin to RT's configuration.> By default, newly installed
-plugins are not enabled. On RT 4.2, each plugin should be enabled by
-the C<Plugin()> command:
+B<Add the plugin to RT's configuration.> By default, newly installed plugins
+are not enabled. On RT 4.2 and later, each plugin should be enabled by the
+C<Plugin()> command:
Plugin( 'RT::Extension::Example' );
Plugin( 'RT::Extension::Sample' );
diff --git a/docs/writing_extensions.pod b/docs/writing_extensions.pod
index 10d1466..e274a5e 100644
--- a/docs/writing_extensions.pod
+++ b/docs/writing_extensions.pod
@@ -66,7 +66,7 @@ you're using some sort of version control for your work.
There are several places to put code to provide your new features
and if you follow the guidelines below, you'll make sure things
get installed in the right places when you're ready to use it. These standards
-apply to RT 4.0 and 4.2 and any differences between the two are noted below.
+apply to RT 4.0 through 4.4 and any differences between them are noted below.
=head2 Module Code
-----------------------------------------------------------------------
More information about the rt-commit
mailing list