Timeline for Semantic Versioning - going from one major version to another?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2019 at 8:18 | vote | accept | Andrius | ||
| Mar 29, 2019 at 8:10 | comment | added | David Arno |
@Andrius, that is correct.v0 is a special case. After v1, pre-releases rely on appending some sort of annotation to the version to reflect that it's a pre-release. I've updated the answer to reflect that.
|
|
| Mar 29, 2019 at 8:09 | comment | added | max630 | With CI in use, for any commit can be an internal "release" which should be named somehow and considered by other modules. | |
| Mar 29, 2019 at 8:08 | history | edited | David Arno | CC BY-SA 4.0 |
added 191 characters in body
|
| Mar 29, 2019 at 8:08 | comment | added | Andrius |
So I guess then, first release (if its not stable release), could be 2.0.0-rc or 2.0.0-alpha or whatever? I just got confused by the fact that you start with 0.1.0 and then only bump major version once it is stable (but you still bump unstable releases for 0 major version)
|
|
| Mar 29, 2019 at 8:05 | history | answered | David Arno | CC BY-SA 4.0 |