When reading the incubation policy(1) my understanding is that the "incubating" requirement is a labeling thing for the archive file that gets voted on, and not something that necessarily needs to be part of the version of the release.
Looking at the release management guide(2) it seems implied that the incubating substring is part of the project name and not the version. Of course, I'm just speculating here. Someone with seniority within the ASF might want to chime in, perhaps? /noa 1) http://incubator.apache.org/incubation/Incubation_Policy.html#Releases 2) http://incubator.apache.org/guides/releasemanagement.html On Thu, Jan 10, 2013 at 10:29 PM, Chip Childers <chip.child...@sungard.com>wrote: > On Thu, Jan 10, 2013 at 4:07 PM, Noa Resare <n...@spotify.com> wrote: > > That's great. I'm sorry that I did not do a better job looking for > previous > > discussion on the matter. Oh well. > > No worries... and yes, we're using semver. In fact, that's why so > much attention is being paid to maintaining backward compatibility for > our API right now. We have also agreed that we want to remain on the > major version 4 for our next feature release (4.1.0-incubating) > > Actually, that's another thing to note (if you didn't pick up on it). > We have a requirement that all of our releases (until we graduate) are > "-incubating" release numbers. > -- Engineering Experience, Infrastructure tribe, Spotify
