Agreed. Both podlings and graduated projects might release components that
are at different maturity levels.
So formally incubation status should really be indicated with a different
groupId, not as a version qualifier.
This would however cause unnecessary confusion if/when the project
On Wed, Feb 11, 2015 at 1:01 AM, Stian Soiland-Reyes st...@apache.org wrote:
An incubator release is a kind of pre-release - community wise. But perhaps
you mean this is not ideal for mature projects who were codewise stable
before joining the incubator?
To me the biggest signaling that needs
When you say break, do you mean some software is unable to compare version
numbers correctly, or that we don't comply with the text of
http://semver.org ?
A pre-release version MAY be denoted by appending a hyphen and a series
of dot separated identifiers immediately following the patch version.
Since the only official release is the source release, perhaps that's
the only place where we in fact need a policy?
On Tue, Feb 10, 2015 at 9:39 PM, Niclas Hedhman nic...@hedhman.org wrote:
On Wed, Feb 11, 2015 at 7:49 AM, Stian Soiland-Reyes st...@apache.org
wrote:
I think formally the
On Wed, Feb 11, 2015 at 7:49 AM, Stian Soiland-Reyes st...@apache.org
wrote:
I think formally the requirement is just that there is incubating
somewhere in the released downloadables, it doesn't have to be part of
the version number
Originally it was a matter of the user can't avoid notice
On Tue, Feb 10, 2015 at 6:50 PM, Benson Margulies bimargul...@gmail.com wrote:
Since the only official release is the source release, perhaps that's
the only place where we in fact need a policy?
I would really encourage us to keep this for Maven. Especially for Maven
where you may have no clue
On Tue, Feb 10, 2015 at 9:56 PM, Roman Shaposhnik ro...@shaposhnik.org
wrote:
On Tue, Feb 10, 2015 at 6:50 PM, Benson Margulies bimargul...@gmail.com
wrote:
Since the only official release is the source release, perhaps that's
the only place where we in fact need a policy?
I would really
Hi Incubator,
I'd like some context about the requirement of adding -incubating in the file
name of podling releases.
http://incubator.apache.org/guides/releasemanagement.html
http://incubator.apache.org/guides/release-java.html#best-practice-maven
It seems we require adding -incubating in the
Agree about the worry about breaking semantic versioning. OSGi-wise
for example this is a bit tricky, where you have to do
0.5.3.incubating instead to ensure incubating is a qualifier rather
than part of the 3.
But if the project is publishing Maven artifacts, then I believe it's
pretty clean if
