community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phil Steitz <>
Subject Re: How can we support a faster release cadence?
Date Thu, 13 Feb 2014 05:02:43 GMT
On 2/12/14, 7:23 PM, Marvin Humphrey wrote:
> On Wed, Feb 12, 2014 at 10:46 AM, Phil Steitz <> wrote:
>> I know this looks old-fashioned, even downright anachronistic to
>> "push-hourly-from-CI" people; but deciding *what* to release *as a
>> community* is an important responsibility of ASF PMCs.  Putting
>> things on a rigid schedule basically skips this step, which, IMHO is
>> a core part of our common culture and values.
> Should projects who wish to release on a regular schedule avoid Apache?

I agree with Joe that that is the wrong question to ask.  The right
question is what are the basic principles and values that
*communities* should buy into when deciding to join Apache.  I
proposed a couple of them above.  How releases happen, how policy
compliance is assured are secondary - the main thing communities
need to ask themselves when deciding to join the ASF is do they want
to do open, community-based development the way it is done here.  If
cutting releases on a predetermined schedule is somehow a
"requirement" for them, the first question to ask is "why" and if
there is a good answer to that question then the second question is
how do you do that in a way that is consistent our principles.

> Marvin Humphrey
> .

View raw message