[rt-users] RT 3.0.8

[John Schubert]

> Jesse Vincent wrote:
> 
> >Happy New Year!
> >
> >RT 3.0.8 is now available. This release includes a number of bug fixes,
> >minor improvements, enhanced tests and performance improvements.
> >
> >RT 3.0.8 can be downloaded from:
> >
> >	http://download.bestpractical.com/pub/rt/release/
> >	79cb76b1662988836914aaadc71a5bf6  rt-3-0-8.tar.gz
> >	22ef9ace2f1fad5666a5de91ccc10f73  rt-3-0-8.tar.gz.sig
> >
> >This release of RT is signed with my gpg key with the following
> >id and fingerprint:
> >
> >	70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90
> >
> >Complete change log:
> >
> >rt.3.D000, C0, jesse, Thu Mar 13 20:43:23 2003, RT: Request Tracker, branch 3.0.
> >
> >    Change Delta  Brief Description
> >     355    289	  Minor cleanups to RT cli tool
> >     356    290	  Fixup to rt-setup-database tool for local schema
> >     357    291	  Display.html takes TicketObj; Update.html uses it
> >     358    292	  localization for link text, not whole link
> >     359    293	  ProcessTicketCustomFieldUpdates takes TicketObj
> >     360    294	  Transaction batching
> >     363    295	  protect against reentrancy in Ticket::DESTROY
> >     365    296	  FastCGI fix to make the CLI work
> >     366    297	  #4415: Fix for imporeting merged tickets
> >     368    298	  Regression and upgrade cleanups
> >     367    299	  Ticket creation and updates via the Web UI were sometimes
> >		  encoded wrong
> >     369    300	  CLI tool should pass through orderby arg
> >     371    302	  none
> >     372    303	  Decode uuencoded attachments

Jesse,
Thanks for the great work and the update.  I'm new to RT (relatively) so
I'm curious about the procedure for upgrading.  I took a look at the TAR
file and see a bunch of changes to /sbin and /lib files, however it
extracts to a rt-3-0-8 directory.  Since the standard, default install
directory is /opt/rt3, what's the preferred method of installation?  I
did look for a README and the RT docs on the website but didn't see
anything that could be applied.

Just a suggestion, but maybe with RT4 we could go to a directory
structure where each version resides in it's own directory and then a
sym link from the base directory (root or opt?) takes you to the most
recent

e.g. 

[john at localhost rt3]$  ls -l
drwxr-xr-x   2 root   root  1024  Nov 2  rt1
drwxr-xr-x   2 root   root  1024  Dec 3  rt2
drwxr-xr-x   2 root   root  1024  Jan 2  rt3
drwxr-xr-x   2 root   root  1024  Jan 31 rt3.0.8
lrwxrwxrwx   2 root   root  1024  Jan 31 rt -> rt3.0.8

My apologies if this is already possible and I'm just not savy (or
awake) enough to figure it out. I like this method because if an upgrade
goes awry, it's easy and fast to back out by changing the sym link back.

John