It's in fact an article on how to do software versioning "properly", which we kind of know... The true problem is vaguely defined APIs with vaguely defined beh

It's in fact an article on how to do software versioning "properly", which we kind of know... The true problem is vaguely defined APIs with vaguely defined behaviors which are prone to change/be fixed/be upgraded during minor updates, which do not qualify as "breaking", because no one realises they do break compatibility. So it's not so much about fixing your version numbers, it's about fixing your tests and specs. And only then you might be able to use the right versioning...