> I know that their proposal is to only include breaking changes in the major version, but in my experience lots of products use major versions for marketing purposes, and minor versions for functional changes including both breaking and non-breaking changes.

The solution is one more number: Marketing.Breaking.Feature.Bugfix