incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Dekany <>
Subject Re: [VOTE] Drop incubating requirement of Maven artifacts
Date Mon, 02 Jan 2017 21:46:45 GMT
This vote doesn't allow voters to differentiate projects that start
their life in the Incubator from those coming to the Incubator after
already widely used. So the voter can only allow omitting
"-incubating" for all *kind* of incubating projects or for none of
them, hence I guess people tends to go for the safer option and more
common case. Admittedly, I'm interested in this because of another
project. But here's the same case again with Groovy. They haven't
grown in the Incubator, so they don't use the Apache brand in their
Maven coordinates (org.codehaus.groovy:groovy), so "-incubating" has
no context there. It has elsewhere, where there's "Apache" somewhere.

Monday, January 2, 2017, 10:02:53 PM, John D. Ament wrote:

> The average is currently 2 years (give or take).  Just to level set.
> I find it interesting that you mention Groovy in your response Mark.  Did
> you know that Groovy interpreted the policy the way this vote is trying to
> formalize the policy, and the artifacts published to maven central did not
> include -incubating?
> You'll notice that the 2.4.5 release was put forth to the incubator as
> 2.4.5-incubating, but published as 2.4.5 in maven central.  You could say
> that what this vote is trying to do is help give clearance to podlings that
> what Groovy did is correct.
> I'll also point out that Groovy didn't use Maven as a build tool, as a
> result they may have felt the policy didn't apply.  They used gradle to
> publish to maven central.
> JB, I hope this response helps clarify for you as well.  I want to make
> sure its clear, the purpose of this vote is to remove the -incubating from
> convenience binaries published via maven, which for some reason is singled
> out in the incubator policies.  Other tools (Gradle, Ant, PyPi, C/C++/Make)
> do not have this requirement, so the goal is to align Maven to all the
> other tools.
> It would still be expected that source distributions include -incubating in
> the file name, since that's the official ASF release.
> John
> On Mon, Jan 2, 2017 at 2:43 PM Mark Struberg <>
> wrote:
>> Groovy is a pretty big project and managed to get through incubation in 8
>> months:
>> But I agree that many projects take longer. Sometimes (as with BatchEE)
>> it's pure laziness to not yet have pushed it 'over the line' though :)
>> LieGrue,
>> strub
>> > Am 02.01.2017 um 20:31 schrieb Jim Apple <>:
>> >
>> >> If a project is well setup and mature then it should do incubation in
>> under 6 months, isn't?
>> >
>> > Are you sure? What does the CDF of incubation time look like? How many
>> > finish in 6 months?
>> >
>> > Beam just graduated in 10 months, and several people on this list
>> > seemed to call it a model of incubation:
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> > For additional commands, e-mail:
>> >
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

 Daniel Dekany

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

View raw message