Hey guys,

We’ve been meaning for a long time to upgrade the machine that our project Subversion repository is hosted on. The older machine started giving us some trouble this afternoon, so we went ahead and migrated our Subversion repositories to newer hardware.

Here are the instructions for updating your working copy to the new location:
http://wiki.cerb4.com/wiki/Changing_SVN_Repository_Locations

We also went ahead and set up support for tags and branches since we’re at the point with 4.0 we can start actually using them. In the instructions above you’ll be able to lock your installation to only get ’stable’ (post-QA tested) updates when you run ’svn update’. If you want to always be using the latest development versions there’s a note at the bottom of the docs.

Update: I should also note that ’stable’ is considered Build 622 as of the move. We’ve done our due dillgence testing the build, but you’ll probably get a conflict on the framework.config.php file after updating. If you aren’t familiar with fixing conflicts, the easiest way to clean this up is to copy your framework.config.php file to framework.config.backup.php and then ‘svn revert framework.config.php‘. Then copy your DB_* entries from the top of the backup file into the reverted copy. If you edit the conflict by hand, be sure to ‘svn resolved framework.config.php‘. You can make sure you cleaned everything up with ‘svn status‘.

It’s probably needless to say; but if you don’t use Subversion you can ignore this announcement. ;)

Thanks!

-Jeff@WGM