On 1 July 2011 17:21, Kevin Falcone <[email protected]> wrote: > On Fri, Jul 01, 2011 at 11:28:42AM +0100, Sean McDaid wrote: >> Yeah I can't recreate the issue there, perhaps I haven't created a large >> enough >> ticket. More likely though it is my configuration or data migration - I >> had to upgrade >> from 3.6 - 4.0 in one go. > >> Is there some way to migrate a 3.6 database directly to 4.0 and then >> simply hook >> this into a RT 4.0 install? This was done manually which I'm skeptical >> about. > > Just read all the instructions in README and docs/UPGRADING-(3.6|3.8|4.0) > and make sure you follow all them, there are mysql specific upgrades > AND schema and content changes, all of which must be done. > > issues.bestpractical.com has been upgraded for many many years > > -kevin
So it's OK to do this? We're on 3.8.10 and have a new 4.0.1 fresh install and are re-creating all queues/users etc. and leaving behind all tickets. Can we/should upgrade our 3.8.10 instead? Thanks. -- http://www.suretecsystems.com/services/openldap/ http://www.surevoip.co.uk -------- 2011 Training: http://bestpractical.com/services/training.html
