From Fedora Project Wiki
Line 22: | Line 22: | ||
## Moves ''un-accpeted'' features to Category:ProposedFeature | ## Moves ''un-accpeted'' features to Category:ProposedFeature | ||
## Updates the overall feature summary for the release at Releases/X/FeatureList | ## Updates the overall feature summary for the release at Releases/X/FeatureList | ||
{{Admon/important | Watch your page! | You should have a ''watch'' on your page so you are notified when its category or state changes. Ensure you are logged in, and then click ''watch'' at the top of your feature page.}} |
Revision as of 16:00, 22 July 2008
Feature Acceptance
Definition
Acceptance by FESCo is a sanity check, presumed in most cases to be a formality, to ensure that new features compliment Fedora's guidelines and is manageable, prior to publicizing as officially targeted for the next release.
Feature acceptance is agreement by FESCo that a particular feature is:
- consistent with the goals and policies of Fedora while within the laws governing the corporate entity sponsoring Fedora--Red Hat.
- supported by the Fedora leadership.
- suitable for listing as an Official Feature of the next release of Fedora
- important to track prior to feature freeze and could affect timeliness of release
Process
- The Feature Owner adds the feature page to Category:ProposedFedoraX
- The Feature Wrangler reviews page for completeness and raises for review at next FESCo meeting
- . FESCo reviews individual feature pages and votes to approve or deny the feature.
- More than 50% of voting FESCo members must be in agreement to approve or deny.
- The feature owner or proxy should be in attendance at this FESCo meeting to answer questions or provide clarification.
- After a FESCo vote the Feature Wrangler:
- Adds accepted features to the accepted category (Category:AcceptedFedoraX)
- Moves un-accpeted features to Category:ProposedFeature
- Updates the overall feature summary for the release at Releases/X/FeatureList