Versioning Architecture

In the SAVE-IDE project we are using Subversion to manage the version of different work files. As long as possible we are following the subversion terminology and standards.

The repository is divided into three different parts:

/trunk
/tags
/branches

The different code lines have the folloing meaning:

The code line /trunk is the main code line and is the place where all the development is done.
The code line /branches is for development which cannot be divided into enough small increments to ensure that the cde line will not be broken. Such changes can, for example be new functionality, major rewrite of on e or more parts or some experimental development based on trial and error.
The code line /tags is a placeholder for branches that either are freezed versions or are alpha or beta versions on which only bug fixes or minor changes is allowed. Observe that minor changes is not equal to small changes. Even small changes can have huge impact on the overall behavior.