Dev:2.4/Source/Development/SVN Migration

A migration to CVS to Subversion for source revision control has been contemplated in the past.

Recently development of Blender has changed to where significant changes occur much more frequently and a larger variety of development trees exist. Another significant development is that Chris Want (Hos) is taking a vaction from merging and juggling the different CVS trees. Also subversion has matured since our last investigation, becoming supported in GForge, and having easy to use end user tools developed that are comparble to those available for CVS.

Given these recent changes I believe it makes sense to reevaluate a migration to Subversion.

Subversion enabled gforge (requires apache2)

• http://dforge.cse.ucsc.edu/
• http://dav.cse.ucsc.edu/grase/DAVForgeRedHat
• http://gforge.org/tracker/?func=detail&group_id=1&aid=629&atid=106

End user tools and subversion

Tortoise SVN a drop in replacement for tortoisecvs http://tortoisesvn.tigris.org/

Using XCode with SVN http://maczealots.com/tutorials/xcode-svn/

Migration to and from subversion and CVS as well as maintaining anonymous CVS checkout on a subversion tree http://sam.zoy.org/writings/programming/svn2cvs.html

• MIGUEL LIST OF REQUIREMENTS FOR A NEW source versioning tool http://mail.gnome.org/archives/gnome-hackers/2005-May/msg00023.html
• CASE STUDY - Mono Migration to Subversion http://svn.haxx.se/dev/archive-2004-11/0745.shtml
• Comparison of CVS and SVN http://wiki.gnuarch.org/SubVersionAndCvsComparison and http://www.pushok.com/soft_svn_vscvs.php

-- TomMusgrove - 21 Aug 2005