incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roman Shaposhnik <>
Subject Re: [DISCUSS] Incubator exit criteria
Date Tue, 24 Jun 2014 05:24:24 GMT
On Thu, Jun 19, 2014 at 6:22 AM, Christian Grobmeier
<> wrote:
> I think its not enough to just look at release / committer additions.
> In the case of Wave, there was a committer addition in the past year. Still
> no commits, nor a release. Looking closer you would find that committer was
> added because there was some excitement around at that time, with a lot of
> plans.
> But then people were facing simply too much work for a small team, and
> the motivation then stopped. A deadline wouldn't not help to get out a
> release.
> That being said, I would like to re-suggest my initial thought with one
> modification:
> - no new committer for a year
> - AND no release for a year
> - AND less than 20 emails in a month on dev@
> - AND less than 10 commits/jira modifications in a month
> - AND no way to change this in the next three months (in example: hackathon
> on horizon)

Here's my personal struggle with two of the items on this list:
   - AND less than 20 emails in a month on dev@
   - AND less than 10 commits/jira modifications in a month
I can't fathom how a community that is that active can't put
itself to a task of making a release.

At the ends of the day, the release of an incubating project
is NOT a glorious exercise in putting the final coat of paint
on a flawless product. It is rather a very mundane way sharing
technology with its users community. And after all, growing the
user community is as important as growing the contributing
community. It is only fair that IPMC gently reminds PPMC of that.

Heck, our TLPs practice it (where expectations are arguably
higher) let alone Incubating projects. Take Hadoop as an
example -- in order to make Hadoop 2.x successful the
community decided to put an early alpha releases of
Hadoop 2.0.x out to share the technology with its users.
It was exactly the right decisions and ultimately it resulted
in a much smoother 2.x.y series.

In short -- you don't have to make your releases GA. Alpha
releases are just fine. Still you have to demonstrate that
you are capable of sharing your work with the user
community and doing an alpha/beta/gamma/YNH release
is the only way to do it.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message