Sunday, April 21 2013

Wesnoth-UMC-Dev’s switch to SourceForge’s new Allura platform is now complete. The repository should be working as usual, with the exception of the web interface to SVN, which is currently lagging behind.

Contributors with existing Subversion checkouts of any portion of the repository will need to run a simple command to switch/relocate the base repository URL as required by the migration:

svn switch --relocate https://wesnoth-umc-dev.svn.sourceforge.net/svnroot/wesnoth-umc-dev NEW_URL

Or for Subversion 1.7.x and later:

svn relocate NEW_URL

The value of NEW_URL depends on whether you are a regular contributor with commit access or just a user with read-only access. Contributors should use svn+ssh://USERNAME@svn.code.sf.net/p/wesnoth-umc-dev/code as NEW_URL (replacing USERNAME with your SF.net username). Users should use either svn://svn.code.sf.net/p/wesnoth-umc-dev/code or https://svn.code.sf.net/p/wesnoth-umc-dev/code instead.

For graphical/alternative Subversion clients, you should consult the documentation for the software you are using for information about switching/relocating a checkout’s repository.

Feel free to direct specific support inquiries about the migration process to our support thread in the Wesnoth forums.

Tuesday, April 16 2013

In order to avoid nasty surprises for our repository contributors at an indeterminate point in the future, we are preparing to switch Wesnoth-UMC-Dev to SourceForge’s new Allura platform before automatic upgrades for active projects begin on the 22nd. You can read more details about SourceForge’s upgrade plan in their blog post if you are interested.

We have decided to perform this step ourselves at a determinate time instead: April 20th, 19:00 UTC.

But what does this mean for users and contributors to Wesnoth-UMC-Dev?

Basically, the repository will be closed down for commits at the appointed time. No more commits should be pushed to the repository after that point. Because of the new platform’s design, the URLs used to access our Subversion (SVN) repository will change. The upgrade process itself will take an unspecified amount of time to complete, hopefully no more than eight hours. After that is completed, contributors with commit access will receive a notification email specifying the new URL for the Subversion repository. However, we will keep the new repository closed until we have ensured that everything is in order.

Once the upgrade is complete, users and contributors must reconfigure their SVN checkouts according to instructions we will post on this same channel.