mirror of
https://github.com/semver/semver.git
synced 2026-07-11 03:53:53 -05:00
[GH-ISSUE #577] Explain the motivation behind the minor version #7373
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @samoylovfp on GitHub (Dec 23, 2019).
Original GitHub issue: https://github.com/semver/semver/issues/577
The meaning of the minor version as "adding backwards compatible features" is clear, but the intent to communicate if a new functionality was added is not obvious.
There must be a reason why it was added and the "why use semantic versioning" part of the website sounds like the best place to add it.
One use case I think could illustrate the need for the minor version is when the need arises to roll back to previous version of a library, you can only safely roll back to a version with the same "major.minor" number, since your code might have already used a feature that is present in this "minor" version but is absent from the previous one.
Is there a better explanation for the need of the minor version and does it make sense to add this to the website text as well?
@alexandrtovmach commented on GitHub (Jun 12, 2020):
It's not related to website, moved to main repo