Page History

...

Following introduction is only draft and it is to be reviewed by experienced Igniters.

begin of draft {{

P0. Initializing

Release phases dates are discussed, as release manager during the first discussion. Release Manager should be comitter (or PMC? - TBD).

Moving scope freeze and code freeze dates may be not best option since a lot of contributors synchronize their efforts to make feature completed by particular moment.

See also Release manager Notes, it contains some instructions for a release manager.

P1.1 Implementation and Scope Discussion

Difference between this and the following phase: it is not possible to move in-progress tickets because branches not diverged.

New branch creation moment is not formal, and it can happen just before or simultaneously with scope freeze.  The important thing is announcing this moment and reminding contributors to cherry-pick commits to release branch.

P1.2 Implementation and Scope Finalization

Removing issues from the scope based on estimated dates of completion, importance to release and on community discussion. Private discussion between contributors is possible, but it is recommended to discuss features in public to allow all community members to share their arguments and concerns.

End of this phase is scope freeze.

P2. Rampdown

This phase is some time to complete implementation of features in initial scope. In parallel with implementation, some less important fixes and features are moved to next release. 

End of rampdown is code freeze. Code freeze is based on dates, but the actual time of freeze is determined by announcing.

P3. Stabilization

There only blockers are accepted. Usually it should be approval of release manager to each commit.

Note blockers here is not only a critical bug, but an issue in the product which makes product unstable or non-functioning, performance drop has proven by a benchmark, a security issue, or a regression of existing features.

P4. Voting

}} end of draft

Sending Release For Vote

...