Development Team/Release/Roadmap

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

Sucrose Development

Sucrose 0.83.x is an unstable development series intended for testing and development purposes. Sucrose uses odd minor version numbers to indicate development status, so this unstable 0.83.x series will eventually become the 0.84 stable release.

Schedule

Date	Task	Notes
Sep 1 2008	New goals proposal
Sep 29	New modules proposal
Oct 29	Sucrose 0.83.1 Tarballs Due
Oct 30	Sucrose 0.83.1 Development Release
Nov 20	Sucrose 0.83.2 Tarballs Due
Nov 21	Sucrose 0.83.2 Development Release
Dec 6	Sucrose 0.83.3 Tarballs Due
Dec 7	Sucrose 0.83.3 Development Release
Dec 20	Sucrose 0.83.4 Tarballs Due
Dec 21	Sucrose 0.83 Beta 1 (0.83.4)	Feature, ABI, String freeze
Jan 15	Sucrose 0.83.5 Tarballs Due
Jan 16	Sucrose 0.83 Beta 2 (0.83.5)
Jan 30	Sucrose 0.83.6 Tarballs Due
Jan 31	Sucrose 0.83 Beta 3 (0.83.6)
Feb 12	Sucrose 0.83.7 Tarballs Due
Feb 13	Sucrose 0.83 Release Candidate 1 (0.83.7)
Feb 19	Sucrose 0.83.8 Tarballs Due
Feb 20	Sucrose 0.83 Release Candidate 2 (0.83.8)
Mar 2	Sucrose 0.84 Tarballs Due	Hard code freeze
Mar 3	Sucrose 0.84 Final Release!

Glucose Modules

• etoys
• sugar
• sugar-base
• sugar-datastore
• sugar-presence-service
• sugar-toolkit
• sugar-artwork

Fructose Modules

• chat-activity
• web-activity
• read-activity
• log-activity
• write-activity
• calculate-activity
• terminal-activity
• pippy-activity
• etoys-activity

Glucose Dependencies

• hippo-canvas
• telepathy-glib
• telepathy-gabble
• telepathy-salut
• telepathy-python

Fructose Dependencies

• pyabiword
• hulahop
• squeak

Goals

• Greater Reliability
• Greater Performace
• Collaboration
• Improved Platform
• Sugar everywhere

Other features

• Next generation journal
• Journal entry sharing
• Robust Clipboard
• Make activities rock!
• Shell improvements
• Improving translation and localization support (multiple fallback languages, separable translation packs, "click to translate" in the UI) (cscott)
• Revisiting "content bundles" -- the current API is a mess, doesn't match the documentation on the wiki, is inconsistent with the activity.info format, etc. I'd like to consider (a) merging content and activities -- a bundle ought to be able to have *both* library.info *and* an activity.info, (b) using a content format which is consistent with "offline internet" content -- more or less consider installing content files as pushing stuff into an offline cache, and (c) finally doing dynamic generation of the top-level "home" page so we don't need to run the indexer after installing content bundles. http://wiki.laptop.org/go/9.1.0#Suggestions_from_User:CScott (cscott)
• nss-rainbow (mstone)
• incrementally remove PS functionality

Related documents

• OLPC 9.1 release goals.