[RFC] "http-types" breakage / additions / rework

I think it’s laudable but if people have, in spite of cabal check / hackage , not put upper bounds on their dependency for http-types, you cannot be held responsible.

Bump the major version, that’s the signal that there’ll be breakage, and you have fulfilled your part of the versioning contract with downstream users.

We have an A.B.C.D scheme where A indicates an epoch (radical changes, full revamp of the API) and B indicates a major version (breaking changes but still going in the same known direction). They’re not just for show and some people tend to treat the job of maintainer as forever-butler. Things change, be it people or APIs. That’s why we have version bounds.