Beta Freeze Policy

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (Corrected the freeze process warning to talk about build, not package)
(normalize with other freeze pages)
Line 1: Line 1:
At the beta freeze and there after, 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).  This is the final freeze in a release under development.  Its purpose is to prevent changes while the release is prepared.  Release blocking bugs can still be fixed following the policy below.
+
{{admon/tip|Ignoring the Freeze Process|Ignoring the freeze process and introducing new packages anyway can result in your package being reverted or reduce the chances of receiving an exception}}
  
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 [https://fedorahosted.org/rel-eng/ Trac Space] with the following information: (Note, don't forget to login, or you will not get email notifications of ticket changes)
+
'''FIXME''': make sure we spell out what is special or different about '''Beta''' freeze vs. Alpha or Final freeze
* 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 [[ReleaseEngineering| 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 [[PackageMaintainers/MainPageFesco|  FESCo]] .
+
* The purpose of the Beta freeze is to stop changes to ''Critical Path'' packages (need link) so there is adequate time to prepare and test the Beta release before making it publicly available.   
 +
* Development builds of packages can continue, however they will not be included in the test release unless you request a break of the freeze for your build.
 +
* New packages can still be reviewed, added in CVS and built
 +
 
 +
== Requesting an Exception ==
 +
If believe there is a good reason for you to break the Beta freeze, submit a request for approval to do so by filing a [https://fedorahosted.org/rel-eng/newticket Release Engineering Ticket]. Please include the following information:
 +
* A description of what you want to change
 +
* Rationale for why the change is important enough to be allowed in after the freeze
 +
* The koji build nvr (name-version-release)
 +
* Impact of *not* accepting the change at this point of the schedule
 +
* Information on what testing you've already done on the development to help reduce the risk
  
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.
+
'''FIXME--CONTEXT:'''(existing text) If you have a recent fedora-packager installed, you can just do <code>make tag-request</code>
  
Note that ignoring the freeze process can lead to your build not getting tagged for the freeze tag, and thus not pushed to rawhide and the final release.
+
== Exception Evaluation ==
 +
The [[ReleaseEngineering| Release Engineering team]]  will evaluate your request and provide feedback. 
 +
* Approval comes in the form of ''+1's'' (meaning ''Yes'' or ''I approve''). 
 +
* Two +1's (without any negative feedback or ''-1's'') are necessary to build.  If there is negative feedback, conversation will ensue and a new vote will be taken.
  
If you have a recent fedora-packager installed, you can just do <code>make tag-request</code>
+
If your request is denied, your package will not appear in Rawhide until the freeze ends. If you disagree with Release Engineering's decision you may enter an appeal with [[Fedora_Engineering_Steering_Committee|FESCo]]. To start the appeals process with FESCo [https://fedorahosted.org/fesco/newtplticket create a ticket with FESCo]. 
  
 
[[Category:Release Engineering]]
 
[[Category:Release Engineering]]

Revision as of 20:15, 14 January 2010

Idea.png
Ignoring the Freeze Process
Ignoring the freeze process and introducing new packages anyway can result in your package being reverted or reduce the chances of receiving an exception

FIXME: make sure we spell out what is special or different about Beta freeze vs. Alpha or Final freeze

  • The purpose of the Beta freeze is to stop changes to Critical Path packages (need link) so there is adequate time to prepare and test the Beta release before making it publicly available.
  • Development builds of packages can continue, however they will not be included in the test release unless you request a break of the freeze for your build.
  • New packages can still be reviewed, added in CVS and built

Requesting an Exception

If believe there is a good reason for you to break the Beta freeze, submit a request for approval to do so by filing a Release Engineering Ticket. Please include the following information:

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

FIXME--CONTEXT:(existing text) If you have a recent fedora-packager installed, you can just do make tag-request

Exception Evaluation

The Release Engineering team will evaluate your request and provide feedback.

  • Approval comes in the form of +1's (meaning Yes or I approve).
  • Two +1's (without any negative feedback or -1's) are necessary to build. If there is negative feedback, conversation will ensue and a new vote will be taken.

If your request is denied, your package will not appear in Rawhide until the freeze ends. If you disagree with Release Engineering's decision you may enter an appeal with FESCo. To start the appeals process with FESCo create a ticket with FESCo.