Changes Freeze Policy
Feature Freeze Policy
At Feature Freeze all new features for the release should be substantially complete and in a testable state. The intention of the release process is finish all new feature work by Feature Freeze and test those new features during the test releases; Alpha and Beta.
Features are accounted for at two different levels:
- Feature page promotion and distro coordination--see Fedora Feature Process
- Package level (continue reading)
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.
Some Example Do's and Don't's
Once we hit Feature Freeze, the expectations change about what work should still be happening to your feature. These expectations are based on needing to test your package, test how other pieces of the distribution interact with your package, and test the overall stability, look, and feel of the distro. Here are some example Do's and Don't's of what to do Post-Feature Freeze.
- Do: Have something testable
- Do: Have the the feature significantly complete
- Do: submit bugfixes
- Do not: Enable the feature by default
- Do not: Make changes that cause other software to have to make changes
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 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.
What Happens Next?
The 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 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.