mantisbt:development_scheme
This is an old revision of the document!
Table of Contents
Development scheme (DRAFT)
There are usually two active branches at any given time:
- the stable branch
- the development branch
Release packages from stable and development branches are linked on the home page.
Between releases, the latest code is always available from our CVS
Stable branch policy
The stable branch should receive only the most important bugfixes, so that:
1. the development resources are focused on development branch, avoiding porting efforts when possible. 1. Keep the stable branch __very stable__ and hence safe to upgrade for everybody
1.0.x branch
- bugs with category “security”
- bugs with severity “major” or higher ( for example: deployment stoppers, blank screens, installation issues )
- bugs that are generating a lot of support
if unsure, feel free to ask on the mantisbt-dev mailing list
1. Security Bugs 2. Bugs that are deployment stoppers - blank screens, installation issues, Linux distribution issues. 3. Bugs that are generating a lot of support.
1.1.x branch (HEAD)
- all bugs
- bugs with category “feature”
After 1.1beta1
1.0.x branch
- bugs with category “security”
1.1.x branch (HEAD)
- bugs with severity “major” or higher
- bugs with category “feature” only after discussion in mantisbt-dev
mantisbt/development_scheme.1186073578.txt.gz · Last modified: 2008/10/29 04:31 (external edit)