[Rt-commit] rt branch, 4.0/documentation-reorg, created. rt-4.0.0rc6-87-g505694e

[Alex Vandiver]

The branch, 4.0/documentation-reorg has been created
        at  505694e64744aea2aa813071f412ab77a678aea0 (commit)

- Log -----------------------------------------------------------------
commit 3e3def2fbf212ae7ebec12bc8e9cf2c4797101dc
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Wed Mar 16 11:36:57 2011 -0700

    Remove stub GPG docs; correct docs are already referenced in RT_Config.pm

diff --git a/docs/customizing/gnupg_integration.pod b/docs/customizing/gnupg_integration.pod
deleted file mode 100644
index 805ed1b..0000000
--- a/docs/customizing/gnupg_integration.pod
+++ /dev/null
@@ -1 +0,0 @@
-This topic is described better in `perldoc lib/RT/Crypt/GnuPG.pm`.

commit 505694e64744aea2aa813071f412ab77a678aea0
Author: Alex Vandiver <alexmv at bestpractical.com>
Date:   Wed Mar 16 13:48:30 2011 -0700

    Fold queue subject upgrade into UPGRADING-3.8

diff --git a/docs/UPGRADING-3.8 b/docs/UPGRADING-3.8
index 55d5540..9a1daf3 100644
--- a/docs/UPGRADING-3.8
+++ b/docs/UPGRADING-3.8
@@ -146,9 +146,31 @@ specific instructions for your database.
 
 UPGRADING FROM 3.7.81 and earlier - Changes:
 
-RT::Extension::BrandedQueues has been integrated into core, so you MUST read
-upgrading instructions docs/queue_subject_tag.pod EVEN IF you have not used
-that extension.
+RT::Extension::BrandedQueues has been integrated into core, and the
+handling of subject tags has changed as a consequence.  You will need to
+modify any of your email templates which use the $rtname variable, in
+order to make them respect the per-queue subject tags. To edit your
+templates, log into RT as your administrative user, then click:
+
+    Configuration -> Global -> Templates -> Select -> <Some template name>
+
+The only template which ships with RT which needs updating is the
+"Autoreply" template, which includes this line:
+
+    "There is no need to reply to this message right now.  Your ticket
+    has been assigned an ID of [{$rtname} #{$Ticket->id()}]."
+
+Change this line to read:
+
+    "There is no need to reply to this message right now.  Your ticket
+    has been assigned an ID of { $Ticket->SubjectTag }."
+
+If you were previously using RT::Extension::BrandedQueues, you MUST
+uninstall it before upgrading. In addition, you must run the
+'etc/upgrade/3.8-branded-queues-extension' perl script.  This will
+convert the extension's configuration into the new format.  Finally, in
+templates where you were using the Tag method ($Ticket->QueueObj->Tag),
+you will need to replace it with $Ticket->SubjectTag
 
 RT::Action::LinearEscalate extension has been integrated into core,
 so you MUST uninstall it before upgrading.
diff --git a/docs/customizing/queue_subject_tag.pod b/docs/customizing/queue_subject_tag.pod
deleted file mode 100644
index 1b4112d..0000000
--- a/docs/customizing/queue_subject_tag.pod
+++ /dev/null
@@ -1,75 +0,0 @@
-=head1 Queue subject tags
-
-This document is about the 'Subject Tag' property of a queue. This
-property allows you to use different tags in the subjects of email which
-RT sends.  By default, the C<rtname> option from the configuration file
-is used for all queues; by changing the subject tag on a per-queue
-basis, you can effectively "brand" individual queues in a single RT
-instance.
-
-=head2 Setting the subject tag
-
-In RT's web UI, go to -E<gt> Configuration -E<gt> Queues -E<gt> Select,
-and select the queue to change.  Enter the 'subject tag' you wish, then
-click "save changes."
-
-=head2 Using the subject tag in templates
-
-Usually, you won't need to add any code to your templates to make the
-subject tags work. A tag will automatically be added in the beginning of
-subject before sending email out.
-
-If you want your subject to be "prefix [tag] real subject" like in
-default Autoreply template, you can use the following code in templates
-to control the placement of the subject tag:
-
-    { $Ticket->SubjectTag }
-
-
-=head1 UPGRADING
-
-=head2 For everyone who is upgrading
-
-You need to modify any of your email templates which use
-the $rtname variable. To edit your templates, log into RT
-as your administrative user, then click:
-
-    Configuration -> Global -> Templates -> Select -> <Some template name>
-
-The only template which ships with RT which needs updating is the
-"Autoreply" template, which includes this line:
-
-    "There is no need to reply to this message right now.  Your ticket
-    has been assigned an ID of [{$rtname} #{$Ticket->id()}]."
-
-Change this line to read:
-
-    "There is no need to reply to this message right now.  Your ticket
-    has been assigned an ID of { $Ticket->SubjectTag }."
-
-=head2 For users of RT-Extension-BrandedQueues
-
-RT-Extension-BrandedQueues was an implementation of this functionality
-which is available from CPAN for older versions of RT.  The
-functionality was folded into core RT in version 3.8 and above; if you
-are B<UPGRADING> from an older version of RT where you were using this
-extension, follow the instructions below:
-
-1) You MUST uninstall RT-Extension-BrandedQueues before upgrading, or
-reinstall RT into a new directory, and reinstall your local
-customizations. The latter is recommended, as there are many changes in
-RT 3.8 and several extensions have been integrated into core.
-
-2) Ensure that you have a current backup of your RT database, and you
-can restore from it.
-
-3) After upgrading, run the 'etc/upgrade/3.8-branded-queues-extension'.
-perl script.  This will convert the extension's configuration into new
-format.
-
-4) In templates where you were using the Tag method (for example C<<
-$Ticket-E<gt>QueueObj-E<gt>Tag >>), replace it with C<<
-$Ticket->SubjectTag >>, as noted above in L</"Using the subject tag in
-templates">.
-
-=cut

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