> Semver describes pre-1.0.0 versions as well. That is what Rule #4 is about, in fact. I know, but rule 4 doesn't mean anything if there is an explicit "we won

> Semver describes pre-1.0.0 versions as well. That is what Rule #4 is about, in fact. I know, but rule 4 doesn't mean anything if there is an explicit "we wont" intention to ever make switch to 1.0.0 - if you're never going to move past 0.*, you're not semver'ing, you're just using your own "looks like semver, might smell like semver, doesn't taste like semver" scheme. > I agree that this is often an issue. I myself advocated that Cargo start projects out at 1.0.0, like npm, rather than 0.1.0, like Bundler. I lost that battle. I'm sorry to hear that =( > [...] but I doubt that some bold text is going to fix what is ultimately a psychological issue. You'd be surprised how far the authority of a spec goes. A ton of people will have massive opinions until they're confronted with the spec, an authority they recognize, clearly stating that their interpretation is explicitly ruled out. Specs allow people to cede authority to it. And of course, don't let any of that detract from a massive thanks for the semver.org effort, no one can deny it's been a net positive on versioning overall.