Changes

If the Feature is accepted the Release Manager moves the Feature to Feature Accepted <version>, such as, [[:Category:Feature Accepted {{Upcoming Stable Release}}]]. If the feature is denied the Release Manager moves the Feature to [[:Category:Feature Page Incomplete]] for rework or future resubmission.

If the Feature is accepted the Release Manager moves the Feature to Feature Accepted <version>, such as, [[:Category:Feature Accepted {{Upcoming Stable Release}}]]. If the feature is denied the Release Manager moves the Feature to [[:Category:Feature Page Incomplete]] for rework or future resubmission.

== Things you should consider when proposing a feature ==

== Things you should consider when proposing a feature ==

= During the process =

= During the process =

* The Release Manager will send individual reminders and announcements to sugar-devel list as necessary

The feature is included in the release cycle and follows the [[Development_Team/Release/Roadmap | Release schedule]].

* 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 Release Manager will maintain this page. This page will be located at: <nowiki>http://wiki.sugarlabs.org/go/<current release>/Feature List</nowiki>, such as [[{{Upcoming Stable Release}}/Feature List]].

* Complete the feature: The feature must be completed by the Feature Freeze.

* Reminders to developers about upcoming feature deadlines will be sent to sugar-devel.

* Feature pages: The feature page should be updated to reflect the current status of the feature. At Feature Freeze: The "How To Test" and "User Experience" section must be completed so that testing of that feature can begin. The section 'Release Notes' must be completed when the writing of the release notes begins.

* Nag mail to developers with delinquent feature page updates will be emailed privately and shamed in a nice way on sugar-devel.

* One week prior to Beta Freeze all features will be 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 pages should be updated to reflect the current status of the feature.

== Are there deadlines for features? ==

== Are there deadlines for features? ==

** 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.

** 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.

** defined criteria for success or failure of the feature.

* 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".  

* 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 Release Manager will present a final feature status to the release team which the release team will review and comment on

* At ''feature freeze'' the Release Manager 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 Manager at Feature Freeze the final ''accepted Feature'' list (Release Road Map) will be publicly announced.

* After final review by the Release Manager at Feature Freeze the final ''accepted Feature'' list (Release Road Map) will be publicly announced.

== What is the process for dropping a feature? ==

== What is the process for dropping a feature? ==