| 1 | Release strategy: |
| 2 | * Stable releases are created on a time schedule: every six months |
| 3 | * Release Candidate 1 is build two weeks after RC0 |
| 4 | * Release Candidate 2 is build two weeks after RC1 |
| 5 | * Final Release is build two weeks after RC2 |
| 6 | |
| 7 | The Technical Steering Committee (TSC) can postpone a release by vote on the mailing list. |
| 8 | |
| 9 | Branch strategy: |
| 10 | * Trunk is for development and is automatically build with uneven version numbers |
| 11 | * Even numbered branch is created from trunk on code freeze (version RC0) |
| 12 | * Automated builds based on trunk will use the next uneven version number immediately after code freeze |
| 13 | * Fixes are committed to both trunk and even numbered branch |
| 14 | * Release Candidates are build from the even numbered branch |
| 15 | |