3,267
edits
Changes
Jump to navigation
Jump to search
Line 88:
Line 88: − * [[/Status | How do I show the status of a feature I own? ]]+ − + − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
→During the process
= During the process =
= During the process =
* [[/Milestones | Are there deadlines for features? ]]
== How do I show the status of a feature I own? ==
* [[/Dropping | What is the process for dropping a feature? ]]
# Feature pages should be updated to reflect the current status of the feature by the following milestones on the [[Development_Team/Release/Roadmap | Release schedule]]:
#* Alpha Freeze --features not 100% complete at alpha should be updated no less than every two weeks
#* Beta Freeze
# One week prior to Beta Freeze all features will evaluated based on test results to date
# At Beta Freeze all feature pages should be at 100% completion, and if necessary, the feature page adjusted to reflect everything completed (so as to reflect 100% completion).
# Feature Wrangler will send individual reminders and announcements to sugar-devel list as necessary
# A summary status for all the features targeted to a particular release will be collected on a summary page which references and briefly explains the feature.
#* The Feature Wrangler will maintain this page.
#* This page will be located at: http://fedoraproject.org/wiki/Releases/<release number>/FeatureList
# Reminders to developers about upcoming feature deadlines will be sent to sugar-devel
# Nag mail to developers with delinquent feature page updates will be emailed privately and shamed in a nice way on sugar-devel
== Are there deadlines for features? ==
* New features may be proposed (using the guidelines above) and accepted no later than the '''Feature Freeze''' milestone
* By the time of Alpha freeze:
** the "Scope" section of the feature must be fleshed out and well defined so that the extent of the work to be completed is understood.
** defined criteria for success or failure of the feature.
** '''fixme''': need to clarify this section more
* By the time of Alpha Freeze, test plans must be complete.
* New features must be feature complete or close enough to completion by Alpha freeze that a majority of its functionality can be suitably tested--the "feature is testable".
* At ''feature freeze'' the Feature Wrangler will present a final feature status to the release team which the release team will review and comment on
* After final review by the release team at Feature Freeze the final ''accepted Feature'' list (Release Road Map) will be publicly announced by the Feature Wrangler.
== What is the process for dropping a feature? ==
A feature will be proposed for a vote to be dropped from the ''Accepted Feature'' list by the release team if one of the following occurs:
* Feature is incomplete or not testable at ''Feature Freeze''
* Feature owner fails to consistently provide status.
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.
= Policy questions =
= Policy questions =