Dunno, I always thought Semantic Versioning specially for projects with breaking changes regularly should be a thing.
I don't like their current system though, Major versions should be reserved for... well... major milestones like reaching the first full featured version or adding a major new feature or completely changing how the thing works. Kind of like a difference between breaking changes one could relatively easily migrate to and breaking changes would require significant work to migrate.
I guess simply leaving off the patch number of a semantic version would be pretty confusing but you get what I mean, a standardized, easily comparable way in the vein of semantic versioning but with only minor and major parts. It should probably have some kind of identifier so it's easy to differentiate from regular semantic versioning, especially since minor changes in semantic versioning shouldn't be breaking. maybe one could a a letter to the minor part or something like that. Like so: "1.b3.3". The "b" indicating a minor version that should be expected to contain breaking changes. Note that there is still a third part for non breaking patches but I would consider that optional.
I don't know if this goes completely against the idea behind semantic versioning, I also don't think it must be this, I'd just like a standard with similar adoption. Ubuntu's system is pretty robust too and if a standardized notation is set then it would be equally easy to compare versions with each other So maybe that can be the standard. In the end what I really want is a system that allows dependency management tools and programmers alike to see at a glance that minor versions may contain breaking changes, similar to how the semantic versioning standard tells us to expect breaking changes with major version. The form of this I don't really care about.
In the end, as long as the version keeps going up instead of down, I'm fine with it. It may be a bit inconvenient but it's like there's a risk to accidentally confuse a new release for an older one.
100
u/crabmusket Aug 21 '20
IMO if you're not doing semver, do calendar versioning like Ubuntu (YY.MM) or dgraph.