[Openvas-commits] r13162 - trunk/doc

[scm-commit at wald.intevation.org]

Author: jan
Date: 2012-03-28 11:41:54 +0200 (Wed, 28 Mar 2012)
New Revision: 13162

Modified:
   trunk/doc/howto-release.txt
Log:
extended howto for release with a short guide for doing branches.


Modified: trunk/doc/howto-release.txt
===================================================================
--- trunk/doc/howto-release.txt	2012-03-28 09:41:04 UTC (rev 13161)
+++ trunk/doc/howto-release.txt	2012-03-28 09:41:54 UTC (rev 13162)
@@ -93,3 +93,24 @@
    when applying simple version comparison.
    Note that we use "+" instead of "-" to help packagers regarding
    the naming scheme of the resulting installation packages.
+
+
+How to branch stable releases
+-----------------------------
+
+To open trunk for a next generation of a OpenVAS module, a branch
+is to be created for the stable version where to maintain further
+patches and releases of the stable version.
+
+Follow these steps for branching:
+
+1. Ensure the module is already in stable (no RC or BETA) phase with at least
+   one public release (e.g. "3.0.0").
+
+2. svn copy svn+ssh://<YOUR_USERNAME>@svn.wald.intevation.org/openvas/trunk/openvas-<MODULE> svn+ssh://<YOUR_USERNAME>@svn.wald.intevation.org/openvas/branches/openvas-<MODULE>-<X>.<X>
+   As commit message use "Creating stable branch <X>.<X> for openvas-<MODULE>.".
+
+3. Edit CMakeLists.txt and increase the major release (MAJOR and or MINOR).
+   Also, switch to beta1 as PATCH version.
+   Commit the change as "Post branch version bump." (see ChangeLog for similar entries).
+