[backport] add v1.6 changelog

[narimiran]

This will be used (linked) from the release article on our website.

Author: @timotheecour

[arnetheduck]

In general, it would be important to include a prominent list of known breaking changes - rn it's hard to find them as they're hidden between bugs and feature additions.

[dom96]

In general, it would be important to include a prominent list of known breaking changes - rn it's hard to find them as they're hidden between bugs and feature additions.

Indeed, that is how we used to do release notes... last I heard we stopped because we don't want people to think that we are breaking things, which is just silly IMO.

[Araq]

Indeed, that is how we used to do release notes... last I heard we stopped because we don't want people to think that we are breaking things, which is just silly IMO.

I don't think that's what I said, but where are the breaking changes for 1.6 anyway? There is one regarding jsonutils which we'll rollback...

[arnetheduck]

want people to think

that sounds really odd though, not at all what I'd expect - ie when you break things, presumably you've thought it through and decide that the pain it causes is worth it, and can stand behind the decision.

re breaking changes, I'm not sure - there was a long list in the devel release notes - if they have all been addressed, fantastic!

I am also thinking about the chronos issue with callbacks, but that's lent which presumably already broke working code in 1.4?

[Araq]

I am also thinking about the chronos issue with callbacks, but that's lent which presumably already broke working code in 1.4?

Correct.

[disruptek]

You broke CPS and my codebase at work. Does that help?

[Araq]

You broke CPS and my codebase at work. Does that help?

No, why did we break these... I cannot document breaking changes I've no clue about.