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. Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. Identifiers MUST NOT be empty. Numeric identifiers MUST NOT include leading zeroes. Pre-release versions have a lower precedence than the associated normal version. A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92. 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? On 10 Feb 2015 23:29, "Julien Le Dem" <jul...@ledem.net> wrote: > 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 version for maven artifacts > which breaks Semantic versioning as hyphen is used for pre-releases. > It is also confusing as we vote on a version number but that's not what we > use as the artifact version. > We are already publishing the source release in the incubator project and > have incubating in its file name as well as DISCLAIMER files. > So it seems to me that adding it in the maven artifact is a bit overkill. > Every release as to get through the vote of the IPMC anyway so it's not > like podlings releases are not vetted appropriately. > > opinions from the IPMC? > > Julien > > > >
