Originally created by @muzir on GitHub (May 9, 2014).
At examples of this entry; there is an example version like "1.0.0-0.3.7" but isn't it a conflict with " Numeric identifiers MUST NOT include leading zeroes" sentence at the same entry? Because this example pre-release is starting with "0" after "-" symbol.
Originally created by @muzir on GitHub (May 9, 2014).
At examples of this entry; there is an example version like "1.0.0-0.3.7" but isn't it a conflict with " Numeric identifiers MUST NOT include leading zeroes" sentence at the same entry? Because this example pre-release is starting with "0" after "-" symbol.
It's not a conflict: the version after the dash (0.3.7) has a major version of 0 (zero), minor version of 3, patch of 7. It's perfectly valid to have a zero as any of the version bits.
@crazedsanity commented on GitHub (May 9, 2014):
It's not a conflict: the version after the dash (0.3.7) has a major version of 0 (zero), minor version of 3, patch of 7. It's perfectly valid to have a zero as any of the version bits.
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 @muzir on GitHub (May 9, 2014).
At examples of this entry; there is an example version like "1.0.0-0.3.7" but isn't it a conflict with " Numeric identifiers MUST NOT include leading zeroes" sentence at the same entry? Because this example pre-release is starting with "0" after "-" symbol.
@crazedsanity commented on GitHub (May 9, 2014):
It's not a conflict: the version after the dash (0.3.7) has a major version of 0 (zero), minor version of 3, patch of 7. It's perfectly valid to have a zero as any of the version bits.
@FichteFoll commented on GitHub (May 9, 2014):
No, the zero in this case is a number by itself. What the clause excludes is things like
01.@jeffhandley commented on GitHub (Jul 9, 2014):
Sounds like this can be closed, @Haacked.