James, I don't believe the question is about not using it. It's required on all source releases. The fundamental question at hand is whether that tag should be applied to generated convenience binaries or not.
Right now, the incubator website says its only required on binaries if you're using maven as your build tool. John On Tue, Jan 3, 2017 at 7:46 AM James Carman <ja...@carmanconsulting.com> wrote: > -1, I like having the indication. I also question why other folks aren't > using it or some other flag to indicate that it's an incubating project. > > > On Mon, Jan 2, 2017 at 12:23 PM John D. Ament <johndam...@apache.org> > 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]: > > > > http://incubator.apache.org/guides/release-java.html#best-practice-maven > > > > >
