User Tools

  • Logged in as: anonymous (anonymous)
  • Log Out

Site Tools


mantisbt:development_scheme

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
mantisbt:development_scheme [2007/09/13 16:11] – removed "s" from end of receive and capitalized "if" in last sentence chillaxmantisbt:development_scheme [2008/10/29 04:25] (current) – external edit 127.0.0.1
Line 8: Line 8:
 Release packages from stable and development branches are linked on the [[http://www.mantisbt.org|home page]]. 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]]
  
  
Line 30: Line 30:
 ===== Development Branch Policy ===== ===== Development Branch Policy =====
  
-The development branch (i.e. 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 development branch reaches a state considered 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)
Line 43: Line 43:
 During feature freeze: 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 development 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   * __ONLY CRITICAL FIXES__ are applied to the stable branch
  
Line 52: Line 52:
   * 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 development resumes on CVS HEAD+  * Normal development resumes on SVN trunk
  
mantisbt/development_scheme.1189714306.txt.gz · Last modified: 2008/10/29 04:31 (external edit)

Driven by DokuWiki