From Fedora Project Wiki
(Feature announcement added to the process) |
(Fix category) |
||
| Line 20: | Line 20: | ||
# No sooner than one week from public announcement, Feature is proposed to FESCo ([[:Category:FeatureReadyForFesco]]) | # No sooner than one week from public announcement, Feature is proposed to FESCo ([[:Category:FeatureReadyForFesco]]) | ||
## Accepted: feature moves to [[:Category:FeatureAcceptedF{{FedoraVersion||next}}]] | ## Accepted: feature moves to [[:Category:FeatureAcceptedF{{FedoraVersion||next}}]] | ||
## Denied: feature moves in Category:FeaturePageIncomplete for rework or future resubmission | ## Denied: feature moves in [[:Category:FeaturePageIncomplete]] for rework or future resubmission | ||
<!-- Not needed since we can use a template function for the release number --> | <!-- Not needed since we can use a template function for the release number --> | ||
Latest revision as of 12:09, 11 December 2012
Feature Process
Individual features are tracked on separate wiki pages in the Features/ namespace. Individual features are organized using categories.
Source: File:Features Policy feature-process-flow2.svg
- New feature ideas may be added at any time to the wiki
- Features/FeatureName (Category:FeaturePageIncomplete)
- New feature desired for a particular release is targeted as such and feature page is complete
- Feature owners believes feature is ready for presentation to FESCo for acceptance
- Features/FeatureName (Category:FeatureReadyForWrangler)
- Feature passes sanity check by Feature Wrangler and is announced on devel-announce mailing list by Feature Wrangler (Category:FeatureAnnounced)
- No sooner than one week from public announcement, Feature is proposed to FESCo (Category:FeatureReadyForFesco)
- Accepted: feature moves to Category:FeatureAcceptedF42
- Denied: feature moves in Category:FeaturePageIncomplete for rework or future resubmission
While allowed by the wiki, a feature should only be assigned to one category.