> I am also okay with following semver but being allowed to release major versions that dont necessarily warrant "breaking changes." Then, to be blunt, you are

> I am also okay with following semver but being allowed to release major versions that dont necessarily warrant "breaking changes." Then, to be blunt, you are not following SemVer > Software has milestones. Lets make them obvious. SemVer is about signalling to clients what expectations they should have by being able to look at your version number changes. If you don't follow it then you are confusing your clients. > If from 0.0.1 to 0.7.4 you had like 5 major changes but nothing was broken API wise those should of been 5 major releases... Anything <1.0.0 is already, by definition, subject to any change so your example is a bit off. However SemVer, in my opinion, is primarily used for libraries that are part of systems of dependency resolution. If you have a desktop app used by end-users then I wouldn't recommend using SemVer, just do what marketing requires.