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-05T17:39:16Z
Lists: pgsql-docs
Andres Freund <andres@anarazel.de> writes: > On 2019-02-05 12:24:00 -0500, Tom Lane wrote: >> Huh? The release note contents are identical cross-branch. >> I know, because I'm generally the one making them. > The point is that links in release-$version.html in /current/ or in a > magical new repo will likely contain references to other pages in the > docs. Yeah, I was just wondering what a separate aggregated-notes document could do with links to pages outside the release notes proper. The low-tech answer would be to remove the links, but it'd be nicer (at least in the HTML version) to make them point over to the main docs. As you say, it'd be good if they pointed to the corresponding version of the main docs, and that's actually something that's broken in our historical process. REL_11_STABLE's copy of release-10.sgml, say, was not linking to the right places. I don't know enough SGML/XML to know if there's some automatic way of rendering <xref linkend="app-pg-dumpall"/> as an external URL. I sure wouldn't care to convert such stuff by hand. 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