You could give us a week as minimum for migration, but you didn't. Now, we have to stop and do it stressfull way. I don't want to continue this thread ... just let you know.
The only way that I could see there being a problem is if you have scheduled an svn up with cron or something in production. But, you would never do this, because one bad commit by anyone would break them.
Before a production release you always have to test any software first.
What is the problem you see? We did exactly this last time we moved svn servers on SF.On 28 Jul 2013 05:49, "Dmitriy Shabanov" <firstname.lastname@example.org> wrote:This is very bad, there are several production servers that depend on svn and now they are in shi... -(On Sat, Jul 27, 2013 at 11:26 PM, <email@example.com> wrote:
Date: 2013-07-27 18:26:23 +0000 (Sat, 27 Jul 2013)
Moved to GitHub, if you want orphaned code from here then checkout the previous revision