incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <>
Subject Re: [VOTE] Drop incubating requirement of Maven artifacts
Date Tue, 03 Jan 2017 06:47:44 GMT

I followed the "other thread" but it's still unclear to me what real
problem this tries to solve.
As others noted, there should be an indicator whether this is already an
official Apache project or in the incubator and adding it to the version
information is the solution with causes the least amount of pain for
users. It's a simple marker, clearly visible for any user.
And once the project is out of the incubator, users simply need to
update to a new version - something which they would do anyway.


John D. Ament wrote
> All,
> I'm calling to vote on a proposed policy change.  Current guide at [1]
> indicates that maven artifacts should include incubator (or incubating) in
> the version string of maven artifacts.  Its labeled as a best practice, not
> a requirement and is not a policy followed on other repository management
> tools (e.g. PyPi).
> I therefore push forward that the incubator will cease expecting java-based
> projects to publish artifacts with "-incubating" in the version string,
> with the understanding that:
> - Incubating is a term used to refer to a project's stability, not a
> release's stability.  It is generally understood that incubating projects
> are not necessarily immature, but may have a potential of failing to become
> a TLP.
> - Podling releases are endorsed, the podling itself is not endorsed.  We
> will not approve releases that are blatantly against ASF policies.
> [ ] +1 Drop the -incubator/-incubating expectation of maven projects
> [ ] +/0
> [ ] -1 Don't drop because....
> [1]:


Carsten Ziegeler
Adobe Research Switzerland

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

View raw message