PVP major version bump guideline

[ju1m]

The decision tree of the Haskell Package Versioning Policy states this guideline:

Which neither resets C to zero (or empty) when incrementing B, nor resets B and C to zero when incrementing A. It likely should to be what's generally expected.

Besides, I can't find a guideline about whether one should increment A or B.
A possible guideline could be:

• when B increments: “there is a breaking change, but if it still compiles, it's probably fine”
• when A increments: “there is a semantic change, please do read the changelog”

Thanks.

[gbaz]

the former is in an update to the pvp, but a new version has not been published: haskell/pvp#31

The latter is purposefully unspecified, because it is not a uniform convention. I'm going to close because further discussion on this or any related issue should be in the pvp repo (which is e.g. where the above issue lives).