The problem we had when trying to push semantic versioning of our app to the rest of the business internally was mostly the fact that breaking changes necessita

The problem we had when trying to push semantic versioning of our app to the rest of the business internally was mostly the fact that breaking changes necessitated a change in the major version, but the business and marketing side wanted control of when a major version could be released. I can see their point, because going from, for example, 1.1.0 to 2.0.0, a user might well expect lots of new features, or at least a significant UI change, and not just "it looks and does the same except for one or two breaking changes". The compromise was to have an architect's vanity number at the front of the Semantic version, so VANITY.MAJOR.MINOR.PATCH