Features/Policy/Dropping

From FedoraProject

< Features | Policy(Difference between revisions)
Jump to: navigation, search
(New page: {{Anchor|drop}} === Dropping Features === A feature will be proposed for a vote to be dropped from the ''Accepted Feature'' list by FESCo if one of the following occurs: * Feature is inc...)
 
(Dropping Features)
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{Anchor|drop}}
 
{{Anchor|drop}}
=== Dropping Features ===
+
== Dropping Features ==
  
A feature will be proposed for a vote to be dropped from the ''Accepted Feature'' list by FESCo if one of the following occurs:
+
A feature will be proposed to FESCo for review  by the Feature Wrangler if any of the following occurs:
 +
* Feature is incomplete (less that 85% complete) or not testable at [[ReleaseEngineering/FeatureFreezePolicy| Feature Freeze]]
 +
* Feature is not complete (100%) at [[Beta_Freeze_Policy | Beta Freeze]]
 +
* Feature owner fails to provide status by updating feature pages at requested milestones.
  
* Feature is incomplete or not testable at ''Feature Freeze''
+
Lacking any response or information from the feature owner, the Feature Wrangler will recommend that features matching this criteria be dropped from the ''Accepted Feature'' list.
* Feature owner fails to consistently provide status or attend IRC meetings (if held).
+
  
Partially completed features can still be listed as ''accepted'' for the upcoming release if the wiki page describing the feature is tailored to reflect the completed work.  Dropped features can be proposed again for inclusion in the next release.
+
Partially completed features may still be listed as ''100%'' complete for a release under development if the wiki page describing the feature is tailored to reflect all of the work that is finishedIncomplete functionality may be rolled forward to a feature page for the next release.  This approach is taken because many people refer to the feature pages after the final release as reference for what is new in the release.  It does not make sense to advertise incomplete work after release day.
 +
 
 +
Dropped features can be proposed again for inclusion in the:
 +
* current release, if proposed before ''Feature Freeze''
 +
* next release under development if proposed two weeks before ''Feature Freeze'' for that release

Latest revision as of 19:18, 23 September 2009

[edit] Dropping Features

A feature will be proposed to FESCo for review by the Feature Wrangler if any of the following occurs:

  • Feature is incomplete (less that 85% complete) or not testable at Feature Freeze
  • Feature is not complete (100%) at Beta Freeze
  • Feature owner fails to provide status by updating feature pages at requested milestones.

Lacking any response or information from the feature owner, the Feature Wrangler will recommend that features matching this criteria be dropped from the Accepted Feature list.

Partially completed features may still be listed as 100% complete for a release under development if the wiki page describing the feature is tailored to reflect all of the work that is finished. Incomplete functionality may be rolled forward to a feature page for the next release. This approach is taken because many people refer to the feature pages after the final release as reference for what is new in the release. It does not make sense to advertise incomplete work after release day.

Dropped features can be proposed again for inclusion in the:

  • current release, if proposed before Feature Freeze
  • next release under development if proposed two weeks before Feature Freeze for that release