Beta Freeze Policy

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
== Beta Freeze Policy ==
 
 
 
At the beta freeze for a release, no new builds are allowed for packages already in the Fedora collection (new packages can still be reviewed, added in CVS and built as potential updates).  The purpose of the final freeze is to prevent changes while the release is prepared.  Release blocking bugs can still be fixed following the policy below.
 
At the beta freeze for a release, no new builds are allowed for packages already in the Fedora collection (new packages can still be reviewed, added in CVS and built as potential updates).  The purpose of the final freeze is to prevent changes while the release is prepared.  Release blocking bugs can still be fixed following the policy below.
  

Revision as of 00:21, 18 September 2009

At the beta freeze for a release, no new builds are allowed for packages already in the Fedora collection (new packages can still be reviewed, added in CVS and built as potential updates). The purpose of the final freeze is to prevent changes while the release is prepared. Release blocking bugs can still be fixed following the policy below.

If you think that you need to break the final freeze, then you should ask for approval after completing the build. To do so, file a ticket in our Trac Space with the following information: (Note, don't forget to login, or you will not get email notifications of ticket changes)

  • The koji build nvr (name-version-release)
  • A description of what you want to change
  • Rationale for why the change is important enough to be allowed in after the final freeze.
  • Impact of *not* accepting the development at this point of the schedule.
  • Information on what testing you've already done on the development to help reduce the risk.

The release team will evaluate the request and provide feedback. If the feature is rejected, then you'll have to submit the build as a post-release update. Disputes over rejected changes can be escalated to FESCo .

Approval will come in the form of +1's. Two +1's (without any negative feedback) are necessary to build. If there is negative feedback, conversation will ensue and a new vote will be issued.

Note that ignoring the freeze process can lead to your package not getting tagged for the freeze tag, and thus not pushed to rawhide and the final release.