Changes

Jump to navigation Jump to search
233 bytes added ,  05:49, 25 November 2009
Line 96: Line 96:     
=== What do the feature owner need to do over the course of the release cycle? ===
 
=== What do the feature owner need to do over the course of the release cycle? ===
# 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]]:
+
The feature is included in the release cycle and follows 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
+
# Complete the feature: The feature must be completed by the Feature Freeze.
# One week prior to Beta Freeze all features will evaluated based on test results to date
+
 
 +
# 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
 
# 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).
 
# 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).
 +
 
# The Release Manager will send individual reminders and announcements to sugar-devel list as necessary
 
# 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.
+
# 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]].
#* 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
+
# 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
+
 
 +
# Nag mail to developers with delinquent feature page updates will be emailed privately and shamed in a nice way on sugar-devel.
    
== Things you should consider when proposing a feature ==
 
== Things you should consider when proposing a feature ==
3,267

edits

Navigation menu