Late to the party, but having a long think about this is sometimes beneficial.
+1 to drop the -incubator/-incubating version attachment for any artifacts (not just Maven). My reasoning is the following: Source code lives longer than any community. Long after a podling has gone through the incubator, the code remains. The releases remain. How a community conducts itself doesn't reflect on the released code. Code just exists. While it is important for current users coming to a project to know the status of the community, does it really matter if the code is in incubation or has graduated? Does that matter in 5 years whether the code of foo-1.2 was incubating while the community has graduated and now resides in the attic? Releases have a long life. Code has a long life. We shouldn't mix timely things like project status with long lived things like releases. Websites are examples of timely, short lived documents and incubation status is a (relatively) short lived state in the long lives of projects. We shouldn't burden the long lived artifacts with the orthogonal status of a project. Martijn On Mon, Jan 2, 2017 at 6:22 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 -- Become a Wicket expert, learn from the best: http://wicketinaction.com --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
