Development Team/Release/Roadmap
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 | Development start | New goals proposal |
Sep 29 | Sucrose 0.83.1 Tarballs Due | New modules proposal |
Sep 30 | Sucrose 0.83.1 Development Release | Finalize modules and goals |
Oct 29 | Sucrose 0.83.2 Tarballs Due | |
Oct 30 | Sucrose 0.83.2 Development Release | |
Nov 20 | Sucrose 0.83.3 Tarballs Due | |
Nov 21 | Sucrose 0.83.3 Development Release | |
Dec 6 | Sucrose 0.83.4 Tarballs Due | |
Dec 7 | Sucrose 0.83.4 Development Release | |
Dec 20 | Sucrose 0.83.5 Tarballs Due | |
Dec 21 | Sucrose 0.83 Beta 1 (0.83.5) | Feature, ABI, String freeze |
Jan 15 | Sucrose 0.83.6 Tarballs Due | |
Jan 16 | Sucrose 0.83 Beta 2 (0.83.6) | |
Jan 30 | Sucrose 0.83.7 Tarballs Due | |
Jan 31 | Sucrose 0.83 Beta 3 (0.83.7) | |
Feb 12 | Sucrose 0.83.8 Tarballs Due | |
Feb 13 | Sucrose 0.83 Release Candidate 1 (0.83.8) | |
Feb 19 | Sucrose 0.83.8 Tarballs Due | |
Feb 20 | Sucrose 0.83 Release Candidate 2 (0.83.9) | |
Mar 2 | Sucrose 0.84 Tarballs Due | Hard code freeze |
Mar 3 | Sucrose 0.84 Final Release! |
Glucose Modules
Fructose Modules
Glucose Dependencies
- hippo-canvas
- telepathy-glib
- telepathy-gabble
- telepathy-salut
- telepathy-python
Fructose Dependencies
- pyabiword
- hulahop
- squeak
Goals
This list looks like features not goals to me.
- Next generation journal
- Collaboration scalability
- Responsive UI
- Shell improvements
- Stable activities API
- Sugar everywhere
- Compatibility with desktop applications
- Quality and reliability
- Robust Clipboard
- Make activities rock!
My suggestion for goals in this release are:
- Greater Reliability and Performance
- Easier to Deploy and Maintain
- Collaboration
From http://wiki.laptop.org/go/9.1.0#Technical_Strategy
I group your list of features in to those goals as follows
- Greater Reliability and Performance
- Responsive UI
- Stable activities API
- Quality and reliability
- Easier to Deploy and Maintain
None
- Collaboration
- Collaboration scalability
The following don't seem to fit the goals of 9.1 (and 8.4?) release. For these I suggest we choose one of the following:
- Find a place in the overall goals
- Create new overall goals and fit them in
- Don't work on these
- Make an exception by defining the user benefit of these and showing demand.
- Next generation journal
- Shell improvements
- Sugar everywhere
- Compatibility with desktop applications
- Robust Clipboard
- Make activities rock!
BTW I hope you don't mind these comments as edits to your page. Back them off and copy to the discussion page if you prefer or let me know how to submit my suggestions. Thanks Gregorio 16:33, 18 September 2008 (UTC)
Ideas
Related documents
- OLPC 9.1 release goals.