Sugar Labs/Roadmap: Difference between revisions

Line 5:

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 ~~organized~~ organizations without introducing excessive amounts of managerial overhead.

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.

==Rational==

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==

@@ Line 5: / Line 5: @@
 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 organized organizations without introducing excessive amounts of managerial overhead.
+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.
+==Rational==
+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==