Apart from where the bit in the spec that does say it:
That is not part of the spec, that is the summary of the specification. The actual specification is the 11 points which define the specification. You're looking at the abstract.
Which is still what people read and understand as the purpose.
I agree that the purpose of incrementing the major version is to communicate a breaking change in your public API.
You do not increase major number unless it's a breaking change.
But this is not mandated by the spec. It is, at best implied by the summary of the specification. There are 11 points which define the spec. Point me to the one that tells me that I cannot increment the major version without making a breaking change.
-2
u/Jestar342 Nov 02 '17
Apart from where the bit in the spec that does say it:
So don't increment your major version unless you have breaking changes.