Adopting semver for releases #130
Unanswered
shawnHartsell
asked this question in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, this project uses calendar based versioning for tags and releases. Calver has several drawbacks, most notably the ability to communicate breaking changes. I'm writing this to gauge the communities/maintainers thoughts on adopting semver instead.
Since this project isn't fast moving I think this can be non in a non-intrusive way. For example, if we decided to do this we can cut a final calendar version and a
v1.0.0at the same SHA and then use semver going forward.Beta Was this translation helpful? Give feedback.
All reactions