Feature Freeze Policy

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Exception Process: Correct a typo)
 
(7 intermediate revisions by 3 users not shown)
Line 2: Line 2:
 
-->
 
-->
  
{{admon/tip|Ignoring the Freeze Process|Ignoring the freeze process and introducing new functionality to approved features anyway can result in your package being reverted or reduce the chances of receiving an exception}}
+
{{admon/tip|Ignoring Feature Freeze|Introducing significant changes to Official Features after Feature Freeze can result in your package being reverted or reduce the chances of receiving an exception}}
  
 
Features are accounted for at two different levels:
 
Features are accounted for at two different levels:
# Feature page promotion and distro coordination--see [[Features/Policy| Fedora Feature Process]]
+
# Feature page promotion and distro coordination -- see [[Features/Policy| Fedora Feature Process]]
 
# Package level (continue reading)  
 
# Package level (continue reading)  
  
Once the ''Feature Freeze'' milestone is reached, all new features for the release should be substantially complete and in a ''testable'' state, and ''enabled by default''--if so specified by the featureIn the Fedora development process, all new feature work is completed by ''Feature Freeze'' and tested during the test releases: Alpha and Beta.
+
Once the ''Feature Freeze'' milestone is reached, all new features for the release should be:
 +
* substantially complete and in a ''testable'' state
 +
* ''enabled by default'' -- if so specified by the feature
 +
 
 +
In the Fedora development process, all new feature work is completed by ''Feature Freeze'' and tested during the test releases: Alpha and Beta.
  
 
== Some Example Do's and Don't's ==
 
== Some Example Do's and Don't's ==
Line 24: Line 28:
  
 
== Exception Process ==
 
== Exception Process ==
If you believe you have a good reason to ''break feature freeze.'' file a ticket with [https://fedorahosted.org/rel-eng/new-ticket Release Engineering]. Breaking ''freature freeze'' means making changes other than simple bug fixes.  We want people to ask before doing this work because it is easier to say "no" than revert changes that have already been made.
+
 
 +
{{admon/caution|Ask First|Before checking in changes and building new packages, please request an exception first.  This saves everyone the time and mess of reverting a change if Release Engineering disagrees with the request.}}
 +
 
 +
If you believe you have a good reason to ''break Feature Freeze.'' file a ticket with [https://fedorahosted.org/fesco/newtplticket FESCo]. Breaking ''Feature Freeze'' means making changes to your package other than simple bug fixes.   
  
 
Please include the following information:  
 
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 be allowed in after the feature freeze.
+
# Rationale for why the change is important enough to be allowed in after the Feature Freeze.
 
# Impact of '''not''' accepting the the new package(s) at this point in the schedule.
 
# Impact of '''not''' accepting the the new package(s) at this point in the schedule.
 
# Information on what testing you've performed to mitigate risks introduced by replacing the existing package(s)
 
# Information on what testing you've performed to mitigate risks introduced by replacing the existing package(s)
  
 
== Exception Evaluation ==
 
== Exception Evaluation ==
The [[ReleaseEngineering| Release Engineering team]]  will evaluate your request and provide feedback.   
+
FESCo will evaluate your request and provide feedback.  This will generally be done in the ticket, and/or in a regular FESCo meeting.
* 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 [[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 09:59, 12 July 2011


Idea.png
Ignoring Feature Freeze
Introducing significant changes to Official Features after Feature Freeze can result in your package being reverted or reduce the chances of receiving an exception

Features are accounted for at two different levels:

  1. Feature page promotion and distro coordination -- see Fedora Feature Process
  2. Package level (continue reading)

Once the Feature Freeze milestone is reached, all new features for the release should be:

  • substantially complete and in a testable state
  • enabled by default -- if so specified by the feature

In the Fedora development process, all new feature work is completed by Feature Freeze and tested during the test releases: Alpha and Beta.

[edit] Some Example Do's and Don't's

After Feature Freeze, Fedora has certain expectations about what will be happening with your feature. These expectations are based on needing to test your feature (package), test how other pieces of the distribution interact with your feature, and test the overall stability, look, and feel of the distribution.

This what we all expect post-Feature Freeze:

  • Do: Have something testable
  • Do: Have the the feature significantly complete
  • Do: submit bugfixes
  • Do not: Continue to add new enhancements
  • Do not: Enable the feature by default (if not already default at Feature Freeze)
  • Do not: Make changes that require other (dependent) software packages to make changes as well

[edit] Exception Process

Stop (medium size).png
Ask First
Before checking in changes and building new packages, please request an exception first. This saves everyone the time and mess of reverting a change if Release Engineering disagrees with the request.

If you believe you have a good reason to break Feature Freeze. file a ticket with FESCo. Breaking Feature Freeze means making changes to your package other than simple bug fixes.

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 Feature Freeze.
  3. Impact of not accepting the the new package(s) at this point in the schedule.
  4. Information on what testing you've performed to mitigate risks introduced by replacing the existing package(s)

[edit] Exception Evaluation

FESCo will evaluate your request and provide feedback. This will generally be done in the ticket, and/or in a regular FESCo meeting.