[sugar] Release schedule and process
Tue May 13 12:24:47 EDT 2008
I think we need to decouple the release cycles between activities and
Sugar to whatever degree possible. Activities should be able to change
at whatever pace is dictated by the activity developers. Since
activities depend upon Sugar, the Sugar schedule needs to be more
predictable. The only time it seems there would be a conflict is when
an incompatible change in a Sugar module is made, which, with the
emerging process, is hopefully rare and well known in advance.
Note that the above says nothing about what constitutes a "core"
activity. But we do want to make sure we are not leaving activity
developers in the dust as we make changes. Sugar without activities is
not very interesting.
On Tue, May 13, 2008 at 12:05 PM, Tomeu Vizoso <tomeu at tomeuvizoso.net> wrote:
> On Mon, May 12, 2008 at 7:03 PM, Marco Pesenti Gritti
> <mpgritti at gmail.com> wrote:
> > On Mon, May 12, 2008 at 7:01 PM, Marco Pesenti Gritti
> > <mpgritti at gmail.com> wrote:
> > > On Mon, May 12, 2008 at 5:37 PM, Tomeu Vizoso <tomeu at tomeuvizoso.net> wrote:
> > > > As any new module/activity will add some overhead to the release team,
> > > > perhaps we should ask that any module included in the release process
> > > > has to provide functionality that the community believes is important
> > > > to the project goals?
> > > >
> > > > So maybe we should ask such a new point:
> > > >
> > > > * Provide functionality that the community judges as important for
> > > > reaching the goals of the project.
> > >
> > > Yeah, I think we will need to define some relevance criteria. I wanted
> > > to let those emerge from the concrete activities discussions rather
> > > than defining them upfront... but your generic definition sounds
> > > pretty good, please add it to the wiki so that we keep this in mind.
> > Btw I think a good way to start defining some of those criteria
> > concretely might be a discussion on its.an.education.project list.
> > Also Walter wrote some criteria to determine the core activities which
> > we could reuse in this context.
> Will initiate such a thread. One thing I don't have completely clear
> is the meaning of an activity being part of the Sugar release. Which
> implications has?
> Sugar mailing list
> Sugar at lists.laptop.org
More information about the Sugar-devel