[EMAIL PROTECTED] writes: > I have a production server with svn 1.4 plus trac 0.10.4. > I wolud like to migrate to svn 1.5 + Trac 0.11.1. I plan to setup another > server (test) with 1.5 + 0.11.1, migrate all the data and then switch the > two machine. > > Do you think it's a good idea or it is better to upgrade the already > running server ? > Or use another procedure ?
I have done that upgrade, but in two steps. I don't remember the order, but I did them separately because I felt comfortable about each at different times, not because of any reason about the combination. Upgrading subversion was trivial. I just instructed the packaging system (pkgsrc) to rebuild subversion and everything that depended on it, and I didn't have to do anything else. For trac, I let the packaging system upgrade trac, and then ran the basic and wiki upgrade commands. I did make extra backups before starting. This was uneventful, except that I had to add --no-backup because I'm using the postgresql backend. So it really depends on how production your production server is. I have about 50 users of whom maybe 10-15 would be put out by a few hours of downtime, and the upgrade-in-place plan was good enough for me. If you do use a second machine, I'd clone the first one and upgrade it, writing down your procedure carefully, and then execute the procedure on the first one. Switching machines means you have to make sure the databases are in sync, and it seems safer to upgrade the real one.
pgp863sOpavO5.pgp
Description: PGP signature
