Practical tips for cvs -> svn migration

Checkout: don't forget to add the "trunk" in a path, this is for example the path to the blender sources:

..... /bf-blender/trunk/blender

and to the windows library files:

..... /bf-blender/trunk/lib/windows/

Using "svn co" with these paths create a 'blender' and 'windows' directory in the current directory.

Certificate information:

 - Hostname: svn.blender.org
 - Valid: from Wed, 09 May 2007 07:30:18 GMT until Mon, 05 Nov 2007 07:30:18 GMT
 - Issuer: www.cacert.org, Root CA
 - Fingerprint: e7:27:b7:0a:1c:5d:9b:69:a4:4d:53:19:
                7d:83:76:a6:db:96:05:df

Introduction

Recently we moved the repositories from CVS to Subversion. There are some new rules to play by however the principles stay the same. You checkout the code, make changes and if you have commit rights, you check them back in. What is different is that all the communication is done via https:// and not ssh and pserver (for anonymous checkout). We have also dropped the ssh key setup; instead you will be using your gforge credentials.

Repository access

Access to the repository will go via https:// both for anonymous (read access) and commit access (write access). The main url for the repository is:

https://svn.blender.org/svnroot/<projectname>

Read Access

This project's CVS repository can be checked out through anonymous Subversion. You will need a Subversion client. Most systems have one installed by default, for a list of clients look at the link provided near the end of the document.

To checkout bf-blender:

svn checkout https://svn.blender.org/svnroot/bf-blender/trunk/blender

You will probably see an error message; this informs you about the certificate that is not issued by a trusted authority. However the certificate is fully functional and will ensure secure transit of the data. You can permanently accept this certificate.

After accepting the certificate the sources will be checked out for anonymous users.

Commit Access

 When a coder has demonstrated that they have the necessary skill and desire to create both feature additions and bug fixes, as well as finding a main target area within Blender to focus on, they may seek BF-Commit access. This process can be done as follows:

•     Create patches and submit to bf-committers list serv
•     Get an endorsment of your coding from several of the project managers

Once access to Subversion has been granted you will need to do a full clean checkout, substituting anonymous with your SVN username.

 svn checkout --username MyUserName https://svn.blender.org/svnroot/bf-blender/trunk/blender

Next you will be prompted for a password. This is the password you need to logon to projects.blender.org.
(Note: Subversion will store your password on your local system and use it next time you communicate with the repository.)

Additional information

For an overview of Subversion clients:

subversion.tigris.org/project_packages.html

There are some good books available about Subversion especially the svnbook:

svnbook.red-bean.com
sourceforge.net/docs/E09

More information about Subversion can be found on the Subversions website.

subversion.tigris.org

Enjoy all the goods!