Changes

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:

1. highly user visible changes (beyond artwork or theme changes)

# highly user visible changes (beyond artwork or theme changes)

2. improvements or changes that require non-trivial cross-package integration

# improvements or changes that require non-trivial cross-package integration

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

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

5. noteworthy enough to call out in the release notes  

# noteworthy enough to call out in the release notes

== What is an enhancement? ==

== What is an enhancement? ==