[sugar] Sugar and OLPC release processes
Tue Jul 15 07:15:08 EDT 2008
Thanks for working on this!
I don't have much to add except to say that I'm OK with whatever is the
consensus of "engineering".
I think the Sugar release process and schedule is pretty well defined
and certainly better documented than the XO process and schedule at this
point. I'm working as quickly as possible to get XO processes and dates
in place. Until that is closer to final, I hope we don't slow down or
interfere with the processes Sugar already has in place.
Keep it up and let me know when you think you have agreement. If I can
help with something just name it and call out my name in the e-mail.
Marco Pesenti Gritti wrote:
> I discussed a bit with Michael how to integrate Sugar and OLPC release
> processes. I'm going to summarize the outcoming here.
> * SugarLabs should try to schedule his release a few months before the
> OLPC release target date (something around 2-3 months). That will give
> us enough time to ensure everything is stable before we start
> integrating the new code in the OLPC distribution.
> * Sugar developers employed by OLPC will work on OLPC release
> contracts for all the new features present in the new release.
> * After the first stable release SugarLabs will keep releasing minor
> updates, which will include bug fixes and strings for the OLPC
> * We should make an effort to develop all the features required as
> part of the unstable development cycle. Though there surely will be
> cases where OLPC will need changes outside the normal SugarLabs
> schedule. We will land these in a limited and controlled way both
> during the freeze periods and as part of the stable minor releases.
> I think this is pretty solid. In particular releasing Sugar a few
> months before OLPC will help improving quality. It's really difficult
> to do unstable development and distribution work at the same time.
More information about the Sugar-devel