Features/Sugar 0.90

From Sugar Labs
< Features
Revision as of 15:10, 14 June 2010 by Pbrobinson (talk | contribs) (Created page with '== Summary == Update to the latest Sugar 0.90 stable release. == Owner == ''This should link to your home wiki page so we know who you are'' * Name: [[User:Pbrobinson| Peter R...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


Update to the latest Sugar 0.90 stable release.


This should link to your home wiki page so we know who you are

Current status

  • Targeted release: SoaS v4
  • Last updated: Peter Robinson
  • Percentage of completion: 0%

Detailed Description

We want to provide the latest version of the Sugar desktop environment as well as more activities to allow further building upon the collaborative environment.

Developers interested in working on the Sugar interface or writing activities can have a development platform without needing an XO laptop.

The includes all the core activities included in the Sucrose release.

Benefit to SoaS

Latest upstream Sugar release


Update packages to the latest release, add any new packages as necessary.

UI Design

Defined by upstream.

How To Test

A stna

User Experience

If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.


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, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?

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 your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.


Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.

The below links are not sorted, but are here for reference when this feature proposal is being written up in more detail. Not all of them may be useful, as a warning for the next person to tackle this page. Mchua 19:04, 11 June 2010 (EDT)

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.

Comments and Discussion