These are the slides from a talk; I didn't spend the extra time to change the format or write down what I explained.

After all, I didn't post them here, someone else did :)

I personally think it's best to just follow the links if the title sounds interesting to you.

Fair enough.

I did follow the links, however it is a bit tedious to then make a picture from the endless mountain of comments on each issue, hence the remark.

Heh, I wish everyone would adopt the gold standard in changelogs: Noriyoshi Shinoda's write-ups of changes in Postgres versions.

Example: https://h50146.www5.hpe.com/products/software/oe/linux/mains...

Clear scope, introduction of new features and demonstrations with examples (even of differences between versions)

Christ, this is on the exact opposite extreme. I'm not sure if this is what I would like to dig through for each big release; could be a tad easier to digest.

I mean, I agree. But there's a toc and I usually skip to the sections relevant to my use cases. The only people who should maybe read the entire thing are (in this case) DBAs.

Chapter 2 (Chapter 1 is "About This Document") is "New Features Summary".

Original link is not changelog, but slides from the meetup presentation. Typical Go changelog is here: https://golang.org/doc/go1.13

I think the laravel upgrade guide is better, you see what might actually break or cause unintended behavior and there's a release notes page with a list of new stuff you can choose to use.

https://laravel.com/docs/6.x/upgrade

(warning: pdf link)