mantisbt:development_scheme
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| mantisbt:development_scheme [2007/08/03 03:11] – giallu | mantisbt:development_scheme [2008/10/29 04:25] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| There are usually two active branches at any given time: | 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:// | Release packages from stable and development branches are linked on the [[http:// | ||
| - | Between releases, the latest code is always available from our [[cvs_access|CVS]] | + | Between releases, the latest code is always available from our [[http:// |
| ===== Stable branch policy ===== | ===== Stable branch policy ===== | ||
| - | The stable branch should receive only the most important | + | The stable branch should receive only the most important |
| + | |||
| + | - The development resources are focused on development branch, avoiding porting efforts when possible. | ||
| + | - The stable branch is kept __very stable__ and hence guarantee a safe upgrade path for everybody | ||
| - | - 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 | ||
| For these reasons, we will fix on the stable branch the following kind of issues: | For these reasons, we will fix on the stable branch the following kind of issues: | ||
| - | * bugs with category " | + | * Bugs with category " |
| - | * bugs with severity " | + | * Critical |
| - | * bugs that are generating a lot of support | + | * Bugs that are generating a lot of support |
| + | |||
| + | If unsure, feel free to ask on the mantisbt-dev mailing list | ||
| + | |||
| + | |||
| + | ===== Development Branch Policy ===== | ||
| - | if unsure, feel free to ask on the mantisbt-dev mailing list | + | The development branch (i.e. SVN trunk) is where all the " |
| - | ===== Development | + | Whenever the development |
| - | The development | + | * A new branch is created from SVN trunk |
| + | * A release candidate (RC) is created off this new branch | ||
| + | * The RC branch enters in a "feature freeze" | ||
| + | * Testing | ||
| - | Whenever the developemnt branch reaches a state coinsidered good enough for becoming the " | ||
| - | * a new branch is created from CVS HEAD | + | During |
| - | * a release candidate (RC) is created off this new branch | + | |
| - | * 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 | + | |
| - | 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 | + | * New features can still enter SVN trunk, but all developers are encouraged to help polishing the RC branch before focusing again on the development |
| + | * 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 | ||
| - | At this point __ONLY CRITICAL FIXES_ are applied to the stable branch | ||
| At release time: | At release time: | ||
| - | * the RC branch becomes the new stable branch | + | * The RC branch becomes the new stable branch |
| - | * support | + | * Support |
| - | * normal develpment | + | * Normal development |
mantisbt/development_scheme.1186125086.txt.gz · Last modified: 2008/10/29 04:31 (external edit)