A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version
What does that exactly mean "might not satisfy"? In particular:
If there exist versions, say, 1.0.1, 2.0-alpha and 2.0, does that mean that the pre-release version is not necessarily backwards compatible w/ 1.0.1 nor does 2.0 is backwards compatible w/ 2.0?
If there exist 1.0.1 and 1.1.0-alpha, is the latter backwards compatible w/ the former?
Originally created by @dkrikun on GitHub (Jul 8, 2013).
Original GitHub issue: https://github.com/semver/semver/issues/135
It is stated that:
> A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version
What does that exactly mean "might not satisfy"? In particular:
- If there exist versions, say, `1.0.1`, `2.0-alpha` and `2.0`, does that mean that the pre-release version is not necessarily backwards compatible w/ `1.0.1` nor does `2.0` is backwards compatible w/ `2.0`?
- If there exist `1.0.1` and `1.1.0-alpha`, is the latter backwards compatible w/ the former?
well, its like it says; the 'associated normal version' of 2.0-alpha is 2.0. So the intent is to comply with the rules as version 2.0 but because it is unstable (an alpha version), it's not yet proven that it actually honors those requirements.
Same for 1.1.0-alpha; it intents to be backwards compatible with 1.0.1, but as it is unstable, it might not be.
<!-- gh-comment-id:20590338 -->
@Tieske commented on GitHub (Jul 8, 2013):
well, its like it says; the 'associated normal version' of `2.0-alpha` is `2.0`. So the intent is to comply with the rules as version `2.0` but because it is unstable (an alpha version), it's not yet proven that it actually honors those requirements.
Same for `1.1.0-alpha`; it intents to be backwards compatible with `1.0.1`, but as it is unstable, it might not be.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @dkrikun on GitHub (Jul 8, 2013).
Original GitHub issue: https://github.com/semver/semver/issues/135
It is stated that:
What does that exactly mean "might not satisfy"? In particular:
1.0.1,2.0-alphaand2.0, does that mean that the pre-release version is not necessarily backwards compatible w/1.0.1nor does2.0is backwards compatible w/2.0?1.0.1and1.1.0-alpha, is the latter backwards compatible w/ the former?@Tieske commented on GitHub (Jul 8, 2013):
well, its like it says; the 'associated normal version' of
2.0-alphais2.0. So the intent is to comply with the rules as version2.0but because it is unstable (an alpha version), it's not yet proven that it actually honors those requirements.Same for
1.1.0-alpha; it intents to be backwards compatible with1.0.1, but as it is unstable, it might not be.@dkrikun commented on GitHub (Jul 8, 2013):
Thanks, that makes it clear