Final Freeze Policy

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Typo)
(Reduce number of admonitions, and order the steps for requests)
Line 5: Line 5:
 
* Updated packages become zero day updates in the ''Updates repo''
 
* Updated packages become zero day updates in the ''Updates repo''
  
= Requesting an Exception =
+
== Exceptions ==
  
== 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 you believe there is a good reason for you to break the Beta 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 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
+
 
+
{{admon/tip|Exception Ticket Wizard|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 ==
+
 
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 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]]

Revision as of 14:11, 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

Exceptions

Requesting an exception

If you believe there is a good reason for you to break the Beta 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

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