> > Vendors are also free to support and provide hot-fixes and back ports on > > these unreleased versions, outside of the community's efforts or concerns > > This seems to me like we're endorsing the release of these versions by > downstream maintainers? Even if we decide to modify this proposal and say > "no, we don't endorse that," how do we prevent it? >
We have to be explicit that semantic versioning != releases. That only some version numbers get formal releases attached to them. And only some of those releases get release branches to them. That is, we are separating the concerns of versioning and releases for dev community benefit. I know some Apache projects don't do takeX re-votes on repeated release attempts. Instead they fix the problem (that caused the vote to fail), increment the version, and start a new vote on a new release with a new version. These projects then have versions that are never released, though this example is not to do with semver. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
