====== Release Procedures ======

  * Page with all our older releases downloads: [[http://releases.mozilla.org/pub/mozilla.org/extensions/allpeers_beta/]]

This page describes shortly the life cycle of product releases. In normal phase, all development is done in HEAD of CVS and standard patch processing/review procedure takes place. Please, see [[src:hack:bug_tracking|Bug tracking]] to learn more about how to use target milestones and flags in Bugzilla.

When we're going to make a release, we're in a release phase. Development during release phase should follow this procedures:
  * By the time we make a feature freeze, only code targeted for a given release can be committed to  CVS.
  * After decision has been made, that CVS HEAD contains all code we want to put in the release, we start release phase.
  * New branch is created in CVS (i.e. ALLPEERS_0_60_BRANCH) and first release candidate is built by responsible person
  * Testing of release candidate takes place (see [[test:testing|Testing]])
  * If any bugs are found, they must be fixed and new release candidate is built. This is repeated as needed.
  * Patches to be put in new release candidate should be reviewed and than flag **auto-commit-rc** should be set and patch should be commited into CVS HEAD
  * After this, responsible person performs auto-commit into release branch and new RC can be built.
  * Development on CVS HEAD during this phase is free as long as other procedures are met (patch reviews, target milestones, etc.). Do not use auto commit to HEAD because we would lose information about CVS blame

External developers don't put their code directly into CVS, they use bugzilla and patches, which is reviewed by one of our developers and after approval they're checked in to CVS.