3,267
edits
Changes
Jump to navigation
Jump to search
Line 9:
Line 9: − − == Is there a way to get an exception from this policy? == − Features not meeting the guidelines above may be brought to the Release Manager for review. − + − The feature owner is responsible for watching any owned pages for state changes, using the wiki watch feature.+ − − Current Release Manager: Simon Schampijer − − − = I want to know... = − == What is a feature? == Line 36:
Line 27: − == What is an enhancement? ==+ − Enhancements are: − # Less documented improvements to a Sugar release which do follow the feature process and do not fit the feature definition above − # Added to the release summary by anyone under heading of Other Enhancements. The release summary for each release lives in the following wiki branches:<br> | [[0.82]] | [[0.84]] | [[0.86]] | [[0.88]] | − #* The wiki template, <nowiki>{{Upcoming Stable Release}}</nowiki> can be used for convenience and general references. − − == Is ''<XXX>'' a feature? == − − +
no edit summary
Finally, having new features listed for a release helps to actively promote new Sugar features to the world. As a Sugar developer you benefit from this promotion by attracting testers and more users to make it better.
Finally, having new features listed for a release helps to actively promote new Sugar features to the world. As a Sugar developer you benefit from this promotion by attracting testers and more users to make it better.
== Who is responsible for this process? ==
== Who is responsible for this process? ==
The person responsible for managing the release, the Release Manager, is designated by the community to fulfill the task.
The person responsible for managing the release, the Release Manager, is designated by the community to fulfill the task. The current Release Manager is Simon Schampijer. The feature owner is responsible for watching any owned pages for state changes, using the wiki watch feature.
= What is a feature? =
A feature is defined as a significant change or enhancement to the version of Sugar currently under development that may or may not include new packages.
A feature is defined as a significant change or enhancement to the version of Sugar currently under development that may or may not include new packages.
# noteworthy enough to call out in the release notes
# noteworthy enough to call out in the release notes
It's sometimes easy to mistake new packages, or enhancements, for features. Features have a very specific definition, but here are some questions to ask yourself before engaging the feature process.
It's sometimes easy to mistake new packages, or enhancements, for features. Features have a very specific definition, but here are some questions to ask yourself before engaging the feature process.
# Is this change very visible to end users?
# Is this change very visible to end users?
#* In this case "end user" means "someone in the audience for this change", which could be desktop users, developers, or system administrators.
#* In this case "end user" means "someone in the audience for this change", which could be Sugar users, developers, or system administrators.
# Does this change require intervention?
# Does this change require intervention?
#* This might be a configuration file format change, or something else that will perturb unsuspecting end users.
#* This might be a configuration file format change, or something else that will perturb unsuspecting end users.