incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stian Soiland-Reyes <>
Subject Re: "-incubator" in versions of podling maven artifacts
Date Thu, 12 Feb 2015 09:00:16 GMT
Agreed. Both podlings and graduated projects might release components that
are at different maturity levels.

So formally incubation status should "really" be indicated with a different
groupId, not as a version qualifier.

This would however cause unnecessary confusion if/when the project
graduates, as the groupId would suddenly change.

With different groupIds, Maven would not easily detect the duplicate if a
project somehow pulled in both an incubator and a graduate release

Downstream users would just see there were no further releases beyond the
last incubator one. (Maven renames help, but are still underutilized)

So personally, as a heavy Maven user, I very much still more prefer the
current norm of indicating the incubation status in the version field, even
though it is not quite technically correct by some measures.
On 11 Feb 2015 21:29, "Roman Shaposhnik" <> wrote:

> On Wed, Feb 11, 2015 at 1:01 AM, Stian Soiland-Reyes <>
> wrote:
> > An incubator release is a kind of pre-release - community wise. But
> perhaps
> > you mean this is not ideal for mature projects who were codewise stable
> > before joining the incubator?
> To me the biggest signaling that needs to happen has little to do with
> the quality/maturity
> of the code (which is a subjective metric anyway) but with the fact
> that something coming
> out of org.apache.* groupID is NOT YET a full member of ASF family
> (and worse case
> scenario may never be).
> Thanks,
> Roman.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message