incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino" <hi...@hiramchirino.com>
Subject Re: Release votes (was: [VOTE] Incubator PMC to approve ActiveMQ 4.0 Release)
Date Sat, 03 Jun 2006 02:08:05 GMT
Agreed.  Any tools that help incubating projects get off to the right
start we be a good start.  Even if it's just a check list that has all
the things that have been found to be missing before in previous
attempted releases would be a great idea.

On 6/2/06, Paul Fremantle <pzfreo@gmail.com> wrote:
> I like the idea of automation.
>
> What would be even more helpful would be a default Apache project
> setup, with a maven release target that builds a release in the right
> format.
>
> If the project structure started out with LICENSE, NOTICE, JAR targets
> that put those in META-INF, places to put auxiliary licenses, etc, and
> produced signatures, MD5s, etc from day 1, then podlings would be off
> to a great start.
>
> Also seems like a easier first step than validation.
>
> Paul
>
>
>
>
> On 6/2/06, Jim Jagielski <jim@jagunet.com> wrote:
> >
> > On Jun 2, 2006, at 9:06 AM, Leo Simons wrote:
> >
> > > (this is a rant and the beginnings of a proposal which has nothing
> > > to do
> > > in particular with James, ActiveMQ, or its release)
> > >
> > > On Fri, May 26, 2006 at 01:11:35PM +0100, James Strachan wrote:
> > >> In accordance with the incubator release procedure (see below) the
> > >> ActiveMQ community has voted on and approved the 4.0 release binary.
> > >>
> > >> We would now like to request the permission of the Incubator PMC to
> > >> perform the release.
> > >
> > > Everytime I read something like this I get terribly annoyed. People
> > > are
> > > doing stuff, trying to comply with all kinds of policies, and then
> > > instead
> > > of self-governing they have to go ask permission. Its wrong.
> > > Permission is
> > > something kids ask their parents for. When you need to ask for it,
> > > you're
> > > not self-governing. If we're to have self-governing communities we
> > > need to
> > > have them be like that while incubating. Self-governance is grown, not
> > > "bolted on" after graduation.
> > >
> >
> > Think of the Incubator as sort of a permanent "member" of the PPMC.
> >
> > In any case, it's the release and distribution of s/w which
> > is the most legally significant (well... *one* of them)
> > thing the ASF does. As such, s/w release must have
> > adequate oversight... Since Incubated projects ride that
> > fence of being ASF projects but "not completely" it really
> > requires that the Incubator PMC agree to such releases.
> >
> > No expects that upon graduation, somehow the project
> > is instantly granted the ability for self-governance.
> > Instead, when they reach that stage where they are
> > actively able to self-govern, and are really doing
> > it, then they are ready to graduate.
> >
> > Think of them as baby birds in a nest: we don't kick them out
> > and then expect them to fly. They leave the nest *when*
> > they learn to fly :)
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Regards,
Hiram

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message