Originally created by @phil-davis on GitHub (Oct 29, 2018).
Looking at the spec:
"Precedence for two pre-release versions with the same major, minor, and patch version MUST be determined by comparing each dot separated identifier from left to right until a difference is found as follows: identifiers consisting of only digits are compared numerically and identifiers with letters or hyphens are compared lexically in ASCII sort order. Numeric identifiers always have lower precedence than non-numeric identifiers."
For example, let's say you use some alpha-numeric strings in position 4. According to the spec, they will sort:
Originally created by @phil-davis on GitHub (Oct 29, 2018).
Looking at the spec:
"Precedence for two pre-release versions with the same major, minor, and patch version MUST be determined by comparing each dot separated identifier from left to right until a difference is found as follows: identifiers consisting of only digits are compared numerically and identifiers with letters or hyphens are compared lexically in ASCII sort order. Numeric identifiers always have lower precedence than non-numeric identifiers."
1) For example, let's say you use some alpha-numeric strings in position 4. According to the spec, they will sort:
```
2.0.0-alpha1
2.0.0-alpha10
2.0.0-alpha11
2.0.0-alpha2
2.0.0-alpha3
...
2.0.0-alpha8
2.0.0-alpha9
```
and you will cause some people (who don't read the spec properly) to wonder why alpha releases ``alpha10`` and ``alpha11`` are followed by ``alpha2``
2) A more "recommended" way to "number" a set of "alpha" releases is to do:
```
2.0.0-alpha.1
2.0.0-alpha.2
2.0.0-alpha.3
...
2.0.0-alpha.8
2.0.0-alpha.9
2.0.0-alpha.10
2.0.0-alpha.11
```
in the style of the example in the spec.
Yes?
@phil-davis, unless you have further questions, please close this issue at your earliest possible convenience.
@jwdonahue commented on GitHub (Nov 25, 2018):
Yes, you have listed them in ascending order.
@phil-davis, unless you have further questions, please close this issue at your earliest possible convenience.
Thanks, I was just looking for confirmation of my reading of the spec - and that the example here might help make the situation clear for someone who finds this in future. Closing.
@phil-davis commented on GitHub (Nov 25, 2018):
Thanks, I was just looking for confirmation of my reading of the spec - and that the example here might help make the situation clear for someone who finds this in future. Closing.
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 @phil-davis on GitHub (Oct 29, 2018).
Looking at the spec:
"Precedence for two pre-release versions with the same major, minor, and patch version MUST be determined by comparing each dot separated identifier from left to right until a difference is found as follows: identifiers consisting of only digits are compared numerically and identifiers with letters or hyphens are compared lexically in ASCII sort order. Numeric identifiers always have lower precedence than non-numeric identifiers."
and you will cause some people (who don't read the spec properly) to wonder why alpha releases
alpha10andalpha11are followed byalpha2in the style of the example in the spec.
Yes?
@jwdonahue commented on GitHub (Nov 25, 2018):
Yes, you have listed them in ascending order.
@phil-davis, unless you have further questions, please close this issue at your earliest possible convenience.
@phil-davis commented on GitHub (Nov 25, 2018):
Thanks, I was just looking for confirmation of my reading of the spec - and that the example here might help make the situation clear for someone who finds this in future. Closing.