Changes Freeze Policy

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (1 revision(s))
(30 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 
<!-- page was renamed from Releases/FeatureFreezePolicy
 
<!-- page was renamed from Releases/FeatureFreezePolicy
-->
 
<!-- page was renamed from JeremyKatz/FeatureFreezeDraft
 
 
-->
 
-->
  
== Feature Freeze Policy ==
+
{{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}}
  
As of the feature freeze for a release, no new features or major version bumps are allowed for packages already in the Fedora collection (new packages can still be reviewed, added in CVS and built).  The purpose of the feature freeze is to help ensure that changes have adequate time to be tested as well as to provide some focus on bug-fixing for the release.
+
Features are accounted for at two different levels:
 +
# Feature page promotion and distro coordination -- see [[Changes/Policy| Fedora Release Planning Process]]
 +
# Package level (continue reading)  
  
If you think that you need to break the feature freeze, then you should ask for approval prior to breaking the freeze.  To do so, send an email to rel-eng@fedoraproject.org with the following information.
+
Once the ''Feature Freeze'' milestone is reached, all new features for the release should be:
* A description of what you want to change
+
* substantially complete and in a ''testable'' state
* Rationale for why the change is important enough to be allowed in after the feature freeze.
+
* ''enabled by default'' -- if so specified by the feature
* Impact of *not* accepting the feature at this point of the schedule.
+
* Information on what testing you've already done on the feature to help reduce the risk.
+
  
The [[ReleaseEngineering|  release team]]  will evaluate the request and provide feedback.  If the feature is rejected, then you'll have to wait for the next development cycle to begin to get the change into Fedora packages. Disputes over rejected changes can be escalated to [[PackageMaintainers/MainPageFesco|  FESCo]]
+
In the Fedora development process, all new feature work is completed by ''Feature Freeze'' and tested during the test releases: Alpha and Beta.
  
Approval will come in the form of +1's.  Two +1's (without any negative feedback) are necessary to build.  If there is negative feedback, conversation will ensue and a new vote will be issued.
+
== Some Example Do's and Don't's ==
  
Note that ignoring the freeze process and introducing new features anyway will lead to your package being reverted and a reduction of the chances of an exception being made.
+
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
 +
 
 +
== Exception Process ==
 +
 
 +
{{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:
 +
# A description of what you want to change
 +
# 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.
 +
# Information on what testing you've performed to mitigate risks introduced by replacing the existing package(s)
 +
 
 +
== 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.
 +
 
 +
[[Category:Release Engineering]]

Revision as of 20:11, 27 May 2014


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

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

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)

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.