From Fedora Project Wiki

(Exception Process: Correct a typo)
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<!-- page was renamed from Releases/FeatureFreezePolicy
This page is obsolete, but we cannot automatically redirect you as you may have been looking for different things depending on where you arrived from.
{{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}}
* For the current processes by which Fedora decides exceptions to the development freezes known as '''[[Milestone freezes]]''', see '''[[QA:SOP_blocker_bug_process]]''' and '''[[QA:SOP_freeze_exception_bug_process]]'''.
* For the current policy regarding 'features' in Fedora, including the schedule points by which they are expected to reach certain points of completion, see '''[[Changes/Policy]]'''. The point previously known as the ''Feature Freeze'' is now the ''Changes Checkpoint #2''.
Features are accounted for at two different levels:
* For an overview of the current Fedora development process, see '''[[Fedora_Release_Life_Cycle]]'''.
# Feature page promotion and distro coordination -- see [[Features/Policy| Fedora Feature Process]]
# 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 ==
{{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 [ 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]]

Latest revision as of 18:41, 1 October 2014

This page is obsolete, but we cannot automatically redirect you as you may have been looking for different things depending on where you arrived from.