community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Cutting <>
Subject Re: How can we support a faster release cadence?
Date Sun, 09 Feb 2014 19:03:00 GMT
On Sat, Feb 8, 2014 at 2:44 PM, Henri Yandell <> wrote:
> * Go and fork the project code on GitHub.
> * Put your changes in there and PR them up into the Apache codebase.
> * If others want to, they can PR the code to you, and then you can PR the
> code up to the codebase (or the group of you could work as a community
> preparing PRs).
> * The one pushing into the Apache codebase needs to be confident that the
> code is covered by CLAs.
> * You can release in GitHub whenever you want.
> * The Apache release happens less often and follows the rules.

Keep in mind that if this is in any way a PMC activity then it is part
of Apache trying to circumvent the rest of Apache, i.e., not advised.
A distinct legal entity may indeed fork, re-brand, alter and release
any Apache project using policies it prefers, but this must be clearly
separate from any Apache project.  A subset of a PMC acting as
individuals would be murky territory if they share no common legal
entity outside Apache.


View raw message