Beta Freeze Policy

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 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:

1. A description of what you want to change
2. Rationale for why the change is important enough to be allowed in after the freeze
3. The koji build nvr (name-version-release)
4. Impact of *not* accepting the change at this point of the schedule
5. 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.