Final Freeze Policy

Ignoring the Final Freeze
Ignoring the freeze process and introducing new packages anyway can result in your package being reverted, reduce the chances of receiving an exception, and potentially delay the release.

• After the Final Freeze no changes are allowed to any packages except for critical release blocking bug fixes.
• All changes must go through the exception process
• All other changes are made via zero day updates in the Updates repo
• The Final freeze is to prepare for creating the Release Candidate.

Exceptions

Requesting an exception

If you believe there is a good reason for you to break the Final freeze, you must request an exception.

1. Build and test your package before submitting anything.
   

   Build and test first!
   Do not omit this step.
2. Submit the freeze exception request by filing a Release Engineering Ticket, or by running make tag-request in your package module. 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
   • Description of testing you've already done on the development to help reduce the risk

Evaluating requests for exception

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 ensues and a new vote is taken.

If your request is accepted, your package will be tagged for inclusion in Rawhide.

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.