Subversion 1.4.6 -> 1.5.2 migration - sanity check please

Hi

We are planning to upgrade our svn server from 1.4.6 to 1.5.2. We are checking what is necessary to be done and would be grateful for comments on our plan.

We have multiple repositories (one for each of our projects) in FSFS format.

The plan is:

1) Install svn 1.5.2 onto new server hardware, running under Centos 5.0

2) Notify users and disable access to 1.4.6 server

3) Backup each repository using 'svnadmin dump' (or could use tar - I) and restore onto the new server

4) Run both svnadmin upgrade and svn-populate-node-origins-index on each repository

5) Map existing http: url to point to new server

6) Notify users that new server is up and running.

Users will remain at 1.4.6 client for now. I see no reason for them to commit modified files prior to the upgrade.

Some file locks may be active, do we need to look after those in some special way?

Anything else we've forgotten?

Best regards

David
Received on 2008-09-26 14:55:59 CEST