[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Migration into a different repository

From: Oefelein, Martina <Martina.Oefelein_at_dionex.com>
Date: 2007-04-19 19:14:48 CEST

We want to move a project that started in a separate repository into our main repository, so that we can more easily share code with other projects in that repository. We are not concerned about loosing history, so a simple import/export should do the job. However, I don't want to interrupt people's workflow, so I'm concerned about local modifications in their working copies at the time of migration, how to transfer these into the new working copy. It seems the best way would be to used patches.
So I came up with the following plan:

1. Announce the migration time at least one day in advance
2. Developers should try to get their local modifiations commited before the migration starts (in order to avoid step 9) where possible
3. Notify everyone that the migration is starting
4. Block write access to the old repository
5. Export the latest revision to an empty folder
6. Import that folder into the main repository
7. Notify everyone that the migration is finished
8. Developers should check out a new working copy from the new location
9. Anybody who has uncommited local modifiations that he wants to preserve:

        1. Update the old working copy to HEAD
        2. Create a patch from the old working copy, including all modifications to be preserved
        3. Apply the patch to the new working copy
        4. Commit the changes in the new working copy when they are finished

Am I missing something? Do you think this is a reasonable strategy? We are using TortoiseSVN on Windows.


Received on Thu Apr 19 19:15:10 2007

This is an archived mail posted to the Subversion Users mailing list.