Svn for release managers

From OctopusWiki

Jump to: navigation, search

The development model looks as follows:

  • development usually happens in the trunk
  • for preparing a release (pre, rc versions) a branch is forked using svn cp. Don't fork too early! 
svn cp trunk branches/2.1.x
  • developers are urged to use this branch to stabilize the code. Some developers that need to work on code for after this release (e.g. 3.0) will continue working on the trunk.
  • when the branch is considered of release quality the branch is copied over to the tags folder 
svn cp branches/2.1.x tags/2.1
  • No further modification should happen in the tags folder, e.g. the tags are 1-1 maps of the released tarballs (minus some autotools generated files).
  • bug fixes will happen in branch/2.1 and when enough or important bug fixes have been accumulated the next release is cut off this branch: 
svn cp branches/2.1.x tags/2.1.1

So there is a succeeding svn cp prodecure trunk -> branch/XXX -> tags/YYY.

Retrieved from "http://www.tddft.org/programs/octopus/wiki/index.php/Svn_for_release_managers"
Personal tools