[otrs] 2.2.3 updrade to 2.2.4

[Rob Cas]

Hi,

Not that this helps answer Steve's question, but I'd love to see more  
thorough upgrading instructions. The UPGRADING file is often quite  
confusing and improvements in the following areas would make life  
easier for those of us using the tarballs.

I've recently upgraded from 2.0.4 to 2.2.4 and it was an  
'interesting' experience (as it was the previous time too). In the  
end, it turned out OK, but more detailed and clearly up-to-date  
upgrading documentation would have made it smoother.

The following is meant to be constructive feedback on parts of the  
UPGRADING file:

 > These instructions are for people upgrading OTRS from "2.1" to "2.2".
As Steve has just pointed out, the version numbers are out of date,  
and while the instructions might still be accurate for the latest  
version, it's not clear to those not in the know whether this file  
has been reviewed recently for accuracy against the current release  
of OTRS.

 > *) Install the new release (tar or RPM)
As Steve has just pointed out, it's not clear which of the following  
you should do:
	- do you simply untar over the old installation?
	- do you untar into a new location? And then what?
		How do you integrate the non-database items backed up in the step  
"*) Backup everything (database, Kernel/Config.pm, Kernel/Config/ 
GenericAgent.pm, var/*)" ?
		Can these files safely be copied into the new location, do they  
need to be manually merged?
		What keys have changed in the .pm files? What keys need to be  
migrated/set in the Admin's SysConfig panel?
		etc
	- do you follow the entire INSTALL, INSTALL.webserver document? If  
not, which parts are relevant for an upgrade?
		eg. 	What perl modules need to be upgraded since the last OTRS  
installation?
			What httpd.conf changes need to be made since the last OTRS  
installation?
			etc.


 > *) Log in as 'root at localhost' and select Admin -> SysConfig to  
make sure that OTRS updates the configuration files.
	When you do this, does OTRS run some special upgrade process?
	Or does this mean that you should manually check all the  
configuration settings from your old installation to make sure they  
have been upgraded?
	
	It would be good if OTRS displayed a report (or produced a log file)  
of which settings it had migrated so that you knew specifically which  
ones to check...

Regards,
	Rob.

BTW to the OTRS folks - thanks for making your product freely  
available. We've found it to be reliable and does the job well. Good  
stuff!








 >*) Update the database changes with:
	This sounds good, but many posts on this list indicate that you need  
to run all the DBUpdate scripts from the intermediate installers  
between your existing installation and the new one.
	What is _really_ recommended? (I'd be able to trust the UPGRADING  
file itself if it were visibly up to date ie. reviewed and updated  
with latest version information).

	> Don't worry about the error messages, you can update all previous  
version
	How does the ignorant user distinguish between genuine error  
messages that should not be ignored, and those are are 'normal'? It  
would be great if the script ran error free...
	


--
Bluefish Technologies Pty Ltd

http://www.bluefish444.com

17b Market Street, South Melbourne
Victoria, Australia, 3205

Phone +61 (3) 9682 9477   Fax +61 (3) 9682 9466

This email is confidential and privileged. Only the intended
recipient may access or use it.  If you are not the intended recipient,
please delete this email and notify us promptly. We use virus scanning
software but exclude all liability for viruses or similar in any  
attachment.