Changes Freeze Policy: Difference between revisions

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.

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.
For an overview of the current Fedora development process, see Fedora_Release_Life_Cycle.

@@ 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 ==
-After 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 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''.
-== Exception Process ==
+* For an overview of the current Fedora development process, see '''[[Fedora_Release_Life_Cycle]]'''.
-If you believe you have a good reason to break feature freeze, please ask for approval prior to breaking the freeze.  To do so, file a ticket in the  [https://fedorahosted.org/rel-eng/ Release Engineering Trac Space].
-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 feature at this point of the schedule.
-* Information on what testing you've already done on the feature to help reduce the risk.
-{{Admon/note | Don't forget to login, or you will not get email notifications of ticket changes}}
-== What Happens Next? ==
-The [[ReleaseEngineering| release engineering team]] will evaluate your request and provide feedback.  If your request is rejected, you will have to wait for the next development cycle to add your package to Fedora.  Disputes over rejected changes can be escalated to [[PackageMaintainers/MainPageFesco| FESCo]].
-Approval comes 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 take place.
-{{Admon/caution | 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.}}
-[[Category:Release Engineering]]

Search

Changes Freeze Policy: Difference between revisions

Latest revision as of 18:41, 1 October 2014