I think SemVer 2.0 is a fine starting point, but as others have already
mentioned we need a few more specifics (similar to what is outlined in the
Accumulo API doc you linked [1]).
Generally speaking, I think there are at least three main issues (probably
more) that we need to address regarding ma
Hi Christopher-
Thanks for kicking this off. I think JB’s idea of a PR draft document is the
way to go so we can layout specifics.
In addition to code-level API/SPI changes, I think it is important that we
address boot-time, configuration, and packaging changes that would impact
DevOps teams.
Hi Christopher
Thanks for starting the thread.
We have several different examples on SemVer in Apache projects.
More than pure SemVer, I think we should clearly state and document
what we agreed on ActiveMQ.
Imho, we should:
- major version should focus on breaking changes (user facing)
- minor
