[Framework-Team] Supported Plone Releases
jon at onenw.org
Wed Dec 10 21:57:11 UTC 2008
> -----Original Message-----
> From: framework-team-bounces at lists.plone.org [mailto:framework-team-
> bounces at lists.plone.org] On Behalf Of Wichert Akkerman
> Sent: Wednesday, December 10, 2008 12:53 PM
> To: framework-team at lists.plone.org
> Subject: Re: [Framework-Team] Supported Plone Releases
> Previously Jon Stahl wrote:
> > > -----Original Message-----
> > > From: framework-team-bounces at lists.plone.org
> > > bounces at lists.plone.org] On Behalf Of Steve McMahon
> > > Sent: Wednesday, December 10, 2008 8:31 AM
> > > To: Framework Team
> > > Subject: Re: [Framework-Team] Supported Plone Releases
> > >
> > > > Why bring this up on the framework team list? The framework team
> > not
> > > > a governing body.
> > >
> > > Then, who is? I certainly think that if the framework team makes a
> > > decision on this, it would be widely respected and supported.
> > >
> > > I think that the PF Board would prefer not to make the decision,
> > > order to continue the tradition of the board not governing
> > > development. And, I think the developer list is way too wide open.
> > +1, I believe the board would vastly prefer not to set the precedent
> > making technical decisions about Plone. The Foundation "protects
> > promotes"; the community develops. :-)
> But this is not a technical decision at all. This is a decision about
> our ability and willpower to dedicate resources (skilled manpower) to
> accopmlish something.
True enough. But I think there is a long-standing consensus that
decisions regarding what software gets built and released should rest
with the community, not the board. And the "center of consensus" in the
community is the framework team, especially for decisions that require
focused effort from a few highly skilled people.
Like I said, I think the board is in generally in favor of this. But
that's different from us "deciding" to continue making security fixes to
2.5.x. The community needs to decide to do that if feels it can/should.
And I think the community will tend to follow the framework team's lead
More information about the Framework-Team