Application of Semantic Versioning Specifications Between 1.0.0-alpha and 1.0.0-alpha.1
I have no concrete idea about the main difference between 1.0.0-alpha and 1.0.0-alpha.1 of a system SemVer when it's applied in a real event of the system's development. Can someone explain the application of the two since according to semver.org 1.0.0-alpha < 1.0.0-alpha.1 or, in other words, 1.0.0-alpha is less than 1.0.0-alpha.1 On the other hand, I am specifying the SemVer specification of my system with this setup: 1.0.0-alpha (e.g., initial alpha pre-release) 1.0.1-alpha (e.g., bug fixes alpha pre-release) 1.1.0-alpha (e.g., added functionality in a backward compatible manner alpha pre-release) 2.0.0-alpha (e.g., incompatible API changes alpha pre-release) I was wondering about the key difference between 1.0.0-alpha.1 compared to the pre-release version alpha without dot (.) identifier when it comes to actual system development progress.

I have no concrete idea about the main difference between 1.0.0-alpha
and 1.0.0-alpha.1
of a system SemVer when it's applied in a real event of the system's development.
Can someone explain the application of the two since according to semver.org
1.0.0-alpha < 1.0.0-alpha.1
or, in other words, 1.0.0-alpha
is less than 1.0.0-alpha.1
On the other hand, I am specifying the SemVer specification of my system with this setup:
- 1.0.0-alpha (e.g., initial alpha pre-release)
- 1.0.1-alpha (e.g., bug fixes alpha pre-release)
- 1.1.0-alpha (e.g., added functionality in a backward compatible manner alpha pre-release)
- 2.0.0-alpha (e.g., incompatible API changes alpha pre-release)
I was wondering about the key difference between 1.0.0-alpha.1
compared to the pre-release version alpha
without dot (.) identifier when it comes to actual system development progress.