-1 It makes it clear that those artifacts are not yet stable ASF projects yet (legally + community). If a project is well setup and mature then it should do incubation in under 6 months, isn't?
Any for any other project I find it quite ok to know what you get. Please also check the discussions from back then when we introduced this policy (for a good reason). LieGrue, strub > Am 02.01.2017 um 18:22 schrieb John D. Ament <johndam...@apache.org>: > > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
