After the project was upgraded, the old repository is read-only and developers have to use the new repo for read-write access.
Still, the fact that whoever had old checkouts has to MANUALLY relocate the SVN is very troublesome, especially for a big project who has lots of users, because it is hard to reach out to all the users of such a project.
Is there any way to have the old repo still be read-only, but in the same time keeping it to be automatically in sync with the new repo ? Or perhaps there is some magic that SF can do so that old checkouts automatically move to the new repo, without manual intervention ?
Log in to post a comment.