-1
I understand your point, but, even if it's not in the version, having a
keyword that the project is still in incubation is important (from a
legal perspective, I don't talk about the release itself).
In the version, artifactId or classifier don't matter, however, having
this flag is important IMHO.
Regards
JB
On 01/02/2017 06:22 PM, 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]:
http://incubator.apache.org/guides/release-java.html#best-practice-maven
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
