Changes

== How To Test ==

== How To Test ==

''This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.''

<--This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.

''Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.''

''Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.''

* ''How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?

* ''How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?

* ''What specific actions do I perform to check that the feature is working like it's supposed to?

* ''What specific actions do I perform to check that the feature is working like it's supposed to?

* ''What are the expected results of those actions?''

* ''What are the expected results of those actions?''-->

== User Experience ==

== User Experience ==

== Dependencies ==

== Dependencies ==

''What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like python?''

No further dependencies, only changes in the sugar shell.

== Contingency Plan ==

== Contingency Plan ==

''If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Sugar will not be in jeopardy.''

Defer to 0.88

== Documentation ==

== Documentation ==

''Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved.''

<--Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved.-->

== Release Notes ==

== Release Notes ==

''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the release team and shipped with the release.''

<-- The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the release team and shipped with the release. -->

== Comments and Discussion ==

== Comments and Discussion ==