Final Freeze Policy

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Add section header, use numbered list, add critpath link)
m (Punctuaaaaaaaaaa-tion)
 
(10 intermediate revisions by 4 users not shown)
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/caution|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.}}
  
'''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 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]].
  
* 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.
+
== Exceptions ==
* 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 can still be reviewed, added in CVS and built ('''true?''')
+
  
= Requesting an Exception =
+
=== Requesting an exception ===
 +
If you believe there is a good reason for you to break the Final freeze, you must request an exception.
 +
<ol><li>Build and test your package before submitting anything.
 +
{{admon/important|Build and test first!| Do not omit this step.}}</li>
 +
<li>Submit the freeze exception request by filing a [https://fedorahosted.org/rel-eng/newticket Release Engineering Ticket], or by running <code>make tag-request</code> 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
 +
</li></ol>
  
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:
+
=== Evaluating requests for exception ===
# A description of what you want to change
+
# Rationale for why the change is important enough to potentially delay the final release
+
# The koji build nvr (name-version-release)
+
# Impact of *not* accepting the change
+
# Information on what testing you've already done on the development to help reduce the risk
+
 
+
== Exception Evaluation ==
+
 
The [[ReleaseEngineering| Release Engineering team]]  will evaluate your request and provide feedback.   
 
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'').   
 
* 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.
+
* 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 [[Fedora_Engineering_Steering_Committee|FESCo]]. To start the appeals process with FESCo [https://fedorahosted.org/fesco/newtplticket create a ticket with FESCo].   
+
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]]

Latest revision as of 20:44, 15 January 2010

Stop (medium size).png
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.

[edit] Exceptions

[edit] 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.
    Important.png
    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

[edit] 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.