Changes

Features/Policy (view source)

Revision as of 05:10, 25 November 2009

230 bytes removed , 05:10, 25 November 2009

→‎During the process

Line 125: Line 125:

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

−

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

+

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

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

−

* One week prior to Beta Freeze all features will be evaluated based on test results to date

+

* By the time of Feature freeze:

−

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

−

~~== 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.

−

* 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

−

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

+

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

+

== Important dates ==

+

* New features may be proposed (using the guidelines above) and accepted no later than the '''Feature Freeze''' milestone.

+

* New features must be feature complete or close enough to completion by Feature Freeze that a majority of its functionality can be suitably tested--the "feature is testable".

+

* After the release at Feature Freeze all features will be evaluated based on test results to date.

+

* Possible reversion of a feature is latest at the UI Freeze release.

* The Release Manager 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 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]].

−

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

Line 157: Line 151:

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

+

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.

Erikos

3,267

edits