Branching and Release Management Policy

There are usually two active branches at any given time:

Release packages from stable and development branches are linked on the home page.

Between releases, the latest code is always available from our Subversion repository

Stable branch policy

The stable branch should receive only the most important bug fixes, so that:

  1. The development resources are focused on development branch, avoiding porting efforts when possible.
  2. 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:

If unsure, feel free to ask on the mantisbt-dev mailing list

Development Branch Policy

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:

During feature freeze:

At release time: