Difference between revisions of "Sugar Labs/Roadmap"
m (rational --> rationale (heh)) |
|||
| Line 10: | Line 10: | ||
Release dates up to and including .86 have been determined by the development team. Starting with .88, the release schedule will be determined by the Sugar Labs oversight board. | Release dates up to and including .86 have been determined by the development team. Starting with .88, the release schedule will be determined by the Sugar Labs oversight board. | ||
| − | == | + | ==Rationale== |
The Release cycle is primarily a synchronization and coordination device. It is a iterative device, as such we are not going to get it 'right' the first time. | The Release cycle is primarily a synchronization and coordination device. It is a iterative device, as such we are not going to get it 'right' the first time. | ||
Revision as of 08:03, 5 July 2009
Community Home · Join · Contacts · Resources · FAQ · Roadmap · To Do · Events Calendar
|
NOTICE: This page is a draft in active flux... Please contribute to these contents and discuss issues on the discussion page. |
Sugar Labs Roadmap
The Sugar Labs Roadmap provides a system for all of the individuals and organizations who develop and deploy the Sugar Learning Platform to coordinate their schedules and work flows.
The defining feature of the roadmap is the Release. Approximately every six months, Sugar Labs releases a updated version of the Sugar Learning Platform. Time based releases are effective methods for coordinating the efforts of loosely coupled organizations without introducing excessive amounts of managerial overhead.
Release dates up to and including .86 have been determined by the development team. Starting with .88, the release schedule will be determined by the Sugar Labs oversight board.
Rationale
The Release cycle is primarily a synchronization and coordination device. It is a iterative device, as such we are not going to get it 'right' the first time.
XXX clarify Currently, the primary release cycle driver is the development team. This is not because the development team is most import. It is because it was, and continues to be, a foundation block of the project. Now, it is time to add marketing to the foundation.
The second tier of blocks are the Activities team, Translation team, Documentation team, SoaS team. These teams build on the foundation team to create an enduser user product.
Support tier - Infrastructure, bug squad, deployment and education.
Tie it all together - Oversight, marketing and design.
Project Level
XXX Articulate Project level goals and targets. In general, describe how team level goal and targets affect project goals and targest
Schedule
| Mile Stone | Date | Champion | Notes |
|---|---|---|---|
| .86 String Freeze | TBD | TBD | Necessary for Translators |
| .86 Design Freeze | TBD | TBD | Necessary for Documentors and marketer for screenshots and other visuals |
| .86 Release | 18 Sept 2009 | Simon | Necessary for downstream pickup |
| Unified SoaS release | TBD | Sebastian |
XXX define .86 release date. In general, describe how the various team affect that schedule.
XXX define SoaS release date. In general, describe how the various teams and external organizations affect that schedule.
XXX anything important enough to be listed on this scheudal is important enough to have an assigned champion to insure that it happens on time.
XXX Link to individual team roadmaps.