- Sep 17, 2019
- 555
- 288
I know, when I was doing programming training, we were always told 1.0 is in effect the first public/mass release version around, after that changes to the main number were major updates and the decimal numbers were minor updates. Though this was 20 odd years ago, no idea how they work now, even then it may well be company dependent about these things.Resetting is about the worst thing you can possibly do. There are many debates surrounding how to version things, but in my opinion, two things should always apply:
The rest is up to the developer. There is no need to follow semantic versioning, as that is really only suitable for certain types of projects, and there's not actually that much software out there that follows it. It's just one possible versioning system, not a rule for versioning in general. There should also be no expectation that version 1.0 means final - it may just mean it's a meaningful checkpoint in the progress. There may still be 1.14, 2.0, 7.7, etc after it.
- Higher number is newer. Not necessarily more content or features though, it's for example common in software that some 3.12 version has more features than a 4.0, since it's possibly made from scratch.
- Each version is unique, never two releases with the same version number
Why I said they should reset the version number is the content is basically being reset therefor the version number should be to correspond to the actual content. It as you said though falls to the developer to decide these things.