Final Freeze Policy

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 
{{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}}
 
{{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}}
  
'''FIXME''': make sure we spell out what is special or different about '''Final''' freeze vs. Alpha or Beta freeze
+
* After the Final Freeze no changes are allowed to any packages except for critical release blocking bug fixes all Package
 
+
* The Final freeze is to prepare for creating the [[Release Candidate]].
* The purpose of the Final freeze is to completely stop all changes to [[Critical_Path_Packages]] to create the [[Release Candidate]].  All changes should be minimized to disrupt this process as little as possible.
+
* Updated packages become zero day updates in the ''Updates repo''
* Development builds of packages can continue, however they will not be included in the final release unless you request a break of the freeze for your build.
+
* New packages become zero day updates in the ''Updates repo''
+
  
 
= Requesting an Exception =
 
= Requesting an Exception =
 +
 +
== Requesting an Exception ==
 +
{{admon/note|Build and Test First| If you believe there is a very good reason for you to break the Final Freeze, build and test your package before submitting a request for approval}}
  
 
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:
 
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
 
# A description of what you want to change
# Rationale for why the change is important enough to potentially delay the final release
+
# Rationale for why the change is important enough to be allowed in after the freeze
 
# The koji build nvr (name-version-release)
 
# The koji build nvr (name-version-release)
# Impact of *not* accepting the change
+
# 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
 
# Information on what testing you've already done on the development to help reduce the risk
 +
 +
{{admon/tip|Exception Ticket Wizzard|As a convenience there is a <code>make</code> target called <code>tag-request</code> in your package module that assists in creating a ticket for you}}
  
 
== Exception Evaluation ==
 
== Exception Evaluation ==

Revision as of 03:01, 15 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
  • After the Final Freeze no changes are allowed to any packages except for critical release blocking bug fixes all Package
  • The Final freeze is to prepare for creating the Release Candidate.
  • Updated packages become zero day updates in the Updates repo

Requesting an Exception

Requesting an Exception

Note.png
Build and Test First
If you believe there is a very good reason for you to break the Final Freeze, build and test your package before submitting a request for approval

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
Idea.png
Exception Ticket Wizzard
As a convenience there is a make target called tag-request in your package module that assists in creating a ticket for you

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.