704
edits
Changes
→What is a feature?
Features are usually considered to meet one or more of the following objectives:
Features are usually considered to meet one or more of the following objectives:
# highly user visible changes (beyond artwork or theme changes)
# Highly user visible changes (beyond artwork or theme changes)
# improvements or changes that require non-trivial cross-package integration
# Improvements or changes that require non-trivial cross-package integration
# exciting new capabilities we can trumpet Sugar having -- some of this is good public relations. Some examples might include:
# Exciting new capabilities we can trumpet Sugar having -- some of this is good public relations. Some examples might include:
#* adding of new functionality to the Sugar platform Examples: version support in the datastore, file-sharing
#* Adding of new functionality to the Sugar platform Examples: version support in the datastore, file-sharing
#* work Sugar contributors are doing upstream as part of their work for Sugar
#* Work Sugar contributors are doing upstream as part of their work for Sugar
#* new features from upstream that we are making available in Sugar for the first time
#* New features from upstream that we are making available in Sugar for the first time
# significant enough that if not completed properly or without a proper backup plan could delay the release
# significant enough that if not completed properly or without a proper backup plan could delay the release
# 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.