4 ms·
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.h
by minxomat 7y ago
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/mainstream/support/lcc/pdf/PostgreSQL_12_Beta1_New_Features_en_20190524-1.pdf 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)
- grenoire 7y agoChrist, 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.
- minxomat 7y agoI 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.
- pritambaral 7y agoChapter 2 (Chapter 1 is "About This Document") is "New Features Summary".
- bla3 7y ago(warning: pdf link)
- judge2020 7y agoI 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 https://laravel.com/docs/6.x/upgrade
- divan 7y agoOriginal link is not changelog, but slides from the meetup presentation. Typical Go changelog is here: https://golang.org/doc/go1.13 https://golang.org/doc/go1.13