Archive/Current Events/2008-07-21: Difference between revisions
No edit summary |
m fix camelcase links |
||
| Line 47: | Line 47: | ||
6. Release process: Marco Pesenti Gritti and Michael Stone have been | 6. Release process: Marco Pesenti Gritti and Michael Stone have been | ||
discussing how to integrate the Sugar and OLPC release processes: | discussing how to integrate the Sugar and OLPC release processes: | ||
* | * Sugar Labs should try to schedule its release a few months before the | ||
OLPC release target date (something around 2–3 months). That will give | OLPC release target date (something around 2–3 months). That will give | ||
us enough time to ensure everything is stable before we start | us enough time to ensure everything is stable before we start | ||
| Line 53: | Line 53: | ||
* Sugar developers employed by OLPC will work on OLPC release | * Sugar developers employed by OLPC will work on OLPC release | ||
contracts for all the new features present in the new release. | contracts for all the new features present in the new release. | ||
* After the first stable release | * After the first stable release Sugar Labs will keep releasing minor | ||
updates, which will include bug fixes and strings for the OLPC | updates, which will include bug fixes and strings for the OLPC | ||
release. | release. | ||
* We should make an effort to develop all the features required as | * We should make an effort to develop all the features required as | ||
part of the unstable development cycle. Though there surely will be | part of the unstable development cycle. Though there surely will be | ||
cases where OLPC will need changes outside the normal | cases where OLPC will need changes outside the normal Sugar Labs | ||
schedule. We will land these in a limited and controlled way both | schedule. We will land these in a limited and controlled way both | ||
during the freeze periods and as part of the stable minor releases. | during the freeze periods and as part of the stable minor releases. | ||