Re: complete revision of repository + perms

Julien TOUCHE wrote:
>> I suggest you hotcopy/backup the repository and work out the migration
>> path in a private environment before you spring it on the developers.
>> If after testing, you feel it can all be done in a short period of
>> time, send everyone to lunch at once and spend the hour tweaking the
>> repository. (Checking in all updates might not be a bad idea.)
>
>
> why not, after testing, load a dump of the test/new tree in main svn
> server ?

I suggested you dump the tree for testing so that you could
test/undo/retest the mv/cp/merge commands necessary to get your
repository in order.

Unless you do all your testing during downtime, your developers have
already committed more things to the main server that you don't have in
your test copy. If you want to spend the time trying to merge those
changes into your test repository, go right ahead.

I think personally, I'd just send the developers all out to lunch at
once and clean up the tree during that time. That'd also give you the
rest of the afternoon to get everyones working copies switch'ed or
rebuilt when they return.

-- 
Andrew Thompson
http://aktzero.com/
Interested in a hosted SVN repository? Email me, let's talk...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org