3 ms·
> "A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. Identifiers MUS
by piotrkubisa 10y ago
> "A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]" [1]
I think they should use 0.0.1-pre instead of 0.0.0. The version 0.0.0 I would consider as "the development have not started yet".
[1] http://semver.org/ http://semver.org/
- stephenr 10y agoI think this advice is even more pertinent: > How should I deal with revisions in the 0.y.z initial development phase? > The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release. Source: http://semver.org/#how-should-i-deal-with-revisions-in-the-0yz-initial-development-phase http://semver.org/#how-should-i-deal-with-revisions-in-the-0...
- piotrkubisa 10y agoI don't get it why I got down-voted since I haven't suggested to use 0.0.1-pre. I have just pointed out that is weird to release version with only zeros - we usually take zero as point to "nothing, void" for non-techie folks (most of end-users). Oh If you would search SemVer repository on GitHub then there are some mentions about 0.0.0 [1]. It is interesting point of view but I prefer non-production versions ready as 0.x.y, where x is greater or equal to 1. So yes, the 0.1.0 is way more meaningful and I recommend it. [1] https://github.com/mojombo/semver/issues/221 https://github.com/mojombo/semver/issues/221