Upgrading and Rolling back an upgrade

[Darren]

We are currently using 3.00.27 and are keen to upgrade, but since there have been SO many problems and issues reported by customers about versions later than 3.00.27 - especially functionality stopping working after upgrade, we would like to know if there are any easy/painless routes to follow for upgrade?

And also for reversion to our 3.00.27 installation which we are quite happy with.

We are concerned about losing tickets/users/user groups especially, as we have several customers who monitor their own tickets and want as little downtime as possible.

Has anybody out there got any suggestions on how best we upgrade - do we go stratight to 3.00.90, or follow an upgrade path - 3.00.28-3.00.80-3.00.81-3.00.90?

Anyone?

[tm2000]

Not sure what Kayako would do.. but with our other Zend type installs.. when it comes to an upgrade, we do a dry run.

Meaning we insist on a 7-14 day NEW key for a sub domain and run it parallel with the current install.. That way we see what works, what doesn't and make a call as to when to do the update.. then do it for real..

When we do the cut, we just rename the directory and use a new duplicate Dbase for the upgrade.. That way if it goes sideways, we simply rename /public_html/support_old back to support and the Dbase is in tact..