From Fedora Project Wiki

(Undo revision 48918 by Jkeating (Talk))
No edit summary
 
(36 intermediate revisions by 9 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.
-->
<!-- page was renamed from JeremyKatz/FeatureFreezeDraft
-->


== Feature Freeze Policy ==
* 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''.
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.
* For an overview of the current Fedora development process, see '''[[Fedora_Release_Life_Cycle]]'''.
 
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, file a ticket in our [https://fedorahosted.org/rel-eng/ Trac Space] with the following information: (Note, don't forget to login, or you will not get email notifications of ticket changes)
* 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 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]]  
 
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.
 
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.

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.

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes_Freeze_Policy&oldid=389451"