Migrating SVN servers for committers

The number of committers to our SVN repository and the sheer amount of activity have both skyrocketed this past year. Sun now has over 25 active contributors and Liferay, Inc. has been hiring key developers from all over the world as well. While that means increased productivity overall, it also means that SVN responsiveness is now much more important than it used to be.

SourceForge's SVN services served us well for many years, but now it's time we had our own SVN hardware.

As of yesterday, all SVN write access to SourceForge has been turned off. Committers must now commit to a new SVN repository which will have its changes pushed to SourceForge. That means SourceForge will continue to serve as our public mirror, but committers will have to use another URL.

So if you're a committer and wondered why your commit access stopped working, do this:

svn switch --relocate https://lportal.svn.sourceforge.net/svnroot/lportal svn://svn.liferay.com/repos/public

Your login will no longer by your SourceForge account, but will now be your www.liferay.com screen name and password. Just log into www.liferay.com and on log in, your credentials will automatically be propagated to our SVN server.

And don't worry about your WOL or Ohloh stats. We'll be syncing the SVN author names for everyone.

For those who just want read access to our code, please continue to check it out on SF.net. It'll usually be 10-20 minutes delayed since we use another application called SVK to sync our SVN repositories.

Blogs
Hi Brian,
Is the SF.net sync now? It is still at revision 22958.
Thanks
There was a problem with our SVK server that was doing the syncing.. but it is now syncing. The problem is that SF.net can be really really slow sometimes so that makes the SVK server hang.
Hi Brian,

It seems that it's not sync anymore. in Sourceforge, the last update was 8 days ago .
We're working on fixing it. It's actually SF's fault because our script keeps posting to it, but around the new year, we updated our copyright date from 2008 to 2009, but SF.net is not able to handle the change because too many files changed, so one of our admin guys will have to do a new dump into SF.net to get it back into sync, sorry about that!
Hello,

How can one get to the updated repository. I would like to continue to tryout the new developments. svn://svn.liferay.com/repos/public always denies access and the old repository at sourceforge is no longer being updated. Your feedback will be highly appreciated.

Thanks,
Pius