Subversion Rules

This page describes the use of the Subversion version control system (SVN for short) in the SE working group.

If you are new to version control, please consult the introductory chapters of the SVN book. Below we will refer to this book quite frequently.

If you understand CVS, but are new to Subversion, please consult the Appendix "Subversion for CVS users" in the SVN book.

Quick start

To get up and running with SVN quickly, proceed as follows:

Things to remember while working with Subversion:



We use the following repository:

Directory structure for branches and tags

In order to keep path names short, we do normally not use the SVN convention of having project-level directories called trunk, branches, tags. Instead, we usually collect all branches in one single top-level directory _allbranches and all tags in one single top-level directory _alltags. Use appropriate long names and/or directory hierarchies below this level. Avoid cluttering the namespace. Delete branches and tags if and when they are no longer needed.

Usage issues (client side)

Which client to use

There are quite a number of clients available for SVN, but most of them are not very good.

We use three different clients:

What to put under version control

What NOT to put under version control

Server administration issues

Setting access rights