Differences

This shows you the differences between two versions of the page.

--- mantisbt:development_scheme [2007/08/04 05:23] – giallu
+++ mantisbt:development_scheme [2008/10/29 04:25] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Branching and release management policy (DRAFT)======
+====== Branching and Release Management Policy ======
 There are usually two active branches at any given time:
-  * the stable branch
+  * The stable branch
-  * the development branch
+  * The development branch
 Release packages from stable and development branches are linked on the [[http://www.mantisbt.org|home page]].
-Between releases, the latest code is always available from our [[cvs_access|CVS]]
+Between releases, the latest code is always available from our [[http://sourceforge.net/svn/?group_id=14963|Subversion repository]]
 ===== Stable branch policy =====
-The stable branch should receive only the most important bugfixes, so that:
+The stable branch should receive only the most important bug fixes, so that:
-  - the development resources are focused on development branch, avoiding porting efforts when possible.
+  - The development resources are focused on development branch, avoiding porting efforts when possible.
-  - the stable branch is kept __very stable__ and hence gurantee a safe upgrade path for everybody
+  - The stable branch is kept __very stable__ and hence guarantee a safe upgrade path for everybody
 For these reasons, we will fix on the stable branch the following kind of issues:
-  * bugs with category "security"
+  * Bugs with category "security"
-  * critical bugs like deployment stoppers, blank screens, installation and upgrade issues
+  * Critical bugs like deployment stoppers, blank screens, installation and upgrade issues
-  * bugs that are generating a lot of support
+  * Bugs that are generating a lot of support requests
-if unsure, feel free to ask on the mantisbt-dev mailing list
+If unsure, feel free to ask on the mantisbt-dev mailing list
-===== Development branch policy =====
+===== Development Branch Policy =====
-The development branch (that is, CVS HEAD) is where all the "interesting" things happens; new features and bug fixes are usually applied here first, then tested and ported to the stable branch when deemed necessary.
+The development branch (i.e. SVN trunk) is where all the "interesting" things happens; new features and bug fixes are usually applied here first, then tested and ported to the stable branch when deemed necessary.
-Whenever the developemnt branch reaches a state coinsidered good enough for becoming the "stable" one, the following happens:
+Whenever the development branch reaches a state considered good enough for becoming the "stable" one, the following happens:
-  * a new branch is created from CVS HEAD
+  * A new branch is created from SVN trunk
-  * a release candidate (RC) is created off this new branch
+  * A release candidate (RC) is created off this new branch
-  * the RC branch enters in a "feature freeze" mode (no new features added)
+  * The RC branch enters in a "feature freeze" mode (no new features added)
-  * testing and bug fixing continue on the RC branch until it can be declared stable
+  * Testing and bug fixing continue on the RC branch until it can be declared stable
 During feature freeze:
-  * new features can still enter CVS HEAD, but all developers are encouraged to help polishing the RC branch before focusing again on the develpment branch.
+  * New features can still enter SVN trunk, but all developers are encouraged to help polishing the RC branch before focusing again on the development branch.
-  * no official releases are composed from CVS HEAD (that is, the soon-to-be development branch)
+  * No official releases are composed from SVN trunk (that is, the soon-to-be development branch)
   * __ONLY CRITICAL FIXES__ are applied to the stable branch
@@ Line 49: / Line 50: @@
 At release time:
-  * the RC branch becomes the new stable branch
+  * The RC branch becomes the new stable branch
-  * support ends for the old stable branch
+  * Support ends for the old stable branch
-  * normal develpment resumes on CVS HEAD
+  * Normal development resumes on SVN trunk