3,267
edits
Changes
Jump to navigation
Jump to search
Line 57:
Line 57: − + − + Line 92:
Line 92: − + + +
→Propose a feature for addition into the release cycle
== Propose a feature for addition into the release cycle ==
== Propose a feature for addition into the release cycle ==
The final goal is to have a feature present in a stable release. There are three major steps needed:
The final goal is to have a feature present in a stable release. There are three major steps needed on which the release manager bases his decision to accept a feature or not:
# Owner: The Feature must have a clear owner (The proposer of the feature and the owner can be the same person).
# Owner: The Feature must have a clear owner (The proposer of the feature and the owner can be the same person).
# Community consensus: There should be more YES than NO in the community for this Feature.
# Community consensus: There should be more YES than NO in the community for this Feature.
#* Send an email to sugar-devel mailing list with [FEATURE] tag in the subject asking for feedback. This is to give the community (deployments, developers, teachers etc) the chance to comment.
#* Send an email to sugar-devel mailing list with [FEATURE] tag in the subject asking for feedback. This is to give the community (deployments, developers, teachers etc) the chance to comment.
#* If your feature adds UI or changes the current UI please add as well the [DESIGN] tag to the subject. The Design Team should be involved in the discussion to guarantee a consistent design and a consistent work flow in Sugar.
#* If your feature adds UI or changes the current UI please add as well the [DESIGN] tag to the subject. The Design Team should be involved in the discussion to guarantee a consistent design and a consistent work flow in Sugar. When presenting the feature to the release manager the design must not be ready but the discussion should have been started.
# Documentation: In order to be considered an official feature accepted for the next Sugar release, the feature should be formally documented on a separate wiki page. The wiki page is the same page than the one from above (a blank template is available at [[Features/Feature Template]]). Please make sure it includes the following information.
# Documentation: In order to be considered an official feature accepted for the next Sugar release, the feature should be formally documented on a separate wiki page. The wiki page is the same page than the one from above (a blank template is available at [[Features/Feature Template]]). Please make sure it includes the following information.
#* Summary of the feature
#* Summary of the feature
# supported by the Sugar community
# supported by the Sugar community
# suitable for listing as an Official Feature of the next release of Sugar
# suitable for listing as an Official Feature of the next release of Sugar
# important to track prior to feature freeze and could affect timeliness of release
# important to track prior to feature freeze and could affect timeliness of the release
The release manager does not comment on the actual code. Merging of the Feature code is in agreement with the module maintainer following the Sugar coding guidelines.
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.