Re: Release note trimming: another modest proposal
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>,
Bruce Momjian <bruce@momjian.us>,
Magnus Hagander <magnus@hagander.net>,
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
pgsql-docs@lists.postgresql.org
Date: 2019-02-05T14:12:56Z
Lists: pgsql-docs
Andres Freund <andres@anarazel.de> writes: > For the record: I think this is a terrible idea. Makes it much harder to > figure out what changed when, and requires per-branch incantations to > grep through the log. Uh ... "grep through the log"? The git log output hasn't changed at all. I've personally never found the SGML/HTML release notes to be even slightly useful for search purposes, because they're spread across so many files. This just changes how many copies of those files we have. > That's not to speak of the fact that now it's > just about impossible to reference all releasenotes on the website in a > useful manner now. You can still point to, say, https://www.postgresql.org/docs/devel/release.html There's maybe two more clicks needed to reach any particular back branch from there, but I would not call that "just about impossible". Anyway, if people want something resembling the old presentation, I think the way to get there is to have some sort of aggregate release notes in a separate place on the web site. We'd discussed that briefly upthread, but no one's volunteered to push it through. regards, tom lane
Commits
-
Doc: in each release branch, keep only that branch's own release notes.
- ed64db588a67 9.5.16 landed
- bb428cb11722 9.4.21 landed
- 60b1d6c2a736 9.6.12 landed
- 2b24271153ec 10.7 landed
- 0d13dd371b64 11.2 landed
- 527b5ed1ad46 12.0 landed