|
|
| (23 intermediate revisions by 8 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. |
| -->
| |
|
| |
|
| == 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''. |
| 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)
| |
| | |
| After the ''Feature Freeze'' milestone, 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).
| |
| | |
| At ''Feature Freeze'' all new features for the release should be substantially complete and in a ''testable'' state, including ''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 | |
| * '''Do not''': Make changes that require other (dependent) software packages to make changes as well
| |
| | |
| == 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].
| |
| 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 mitgate risks introduced by replacing the existing package(s)
| |
| | |
| {{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 | Please Follow the Process | Ignoring the freeze process and introducing new features (packages) anyway may lead to your package being reverted and a reduction of the chances of an exception being made.}}
| |
| | |
| [[Category:Release Engineering]]
| |
