Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1gr4gx-00034h-Sv
	for pgsql-docs@arkaria.postgresql.org; Tue, 05 Feb 2019 17:39:28 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1gr4gw-0007pz-96
	for pgsql-docs@arkaria.postgresql.org; Tue, 05 Feb 2019 17:39:26 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1gr4gv-0007pr-W7
	for pgsql-docs@lists.postgresql.org; Tue, 05 Feb 2019 17:39:26 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1gr4gt-0001uz-IM
	for pgsql-docs@lists.postgresql.org; Tue, 05 Feb 2019 17:39:24 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x15HdGi4011158;
	Tue, 5 Feb 2019 12:39:16 -0500
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
Subject: Re: Release note trimming: another modest proposal
In-reply-to: <20190205172817.iatgselxmfeqda5g@alap3.anarazel.de>
References: <16080.1548459680@sss.pgh.pa.us>
 <20190125234614.GH13803@momjian.us>
 <8fd2ae88-49de-26f3-def3-e4381cb7e774@postgresql.org>
 <21920.1548515166@sss.pgh.pa.us>
 <20190205060201.jo3ejddklqxb5a4q@alap3.anarazel.de>
 <72f54463-6912-115e-cb89-1fb552659505@postgresql.org>
 <20190205170150.yim3w67sogqw2dg3@alap3.anarazel.de>
 <9649.1549386657@sss.pgh.pa.us>
 <20190205171707.3ct4ch3q25xg4lpo@alap3.anarazel.de>
 <10393.1549387440@sss.pgh.pa.us>
 <20190205172817.iatgselxmfeqda5g@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Tue, 05 Feb 2019 09:28:17 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <11156.1549388356.1@sss.pgh.pa.us>
Date: Tue, 05 Feb 2019 12:39:16 -0500
Message-ID: <11157.1549388356@sss.pgh.pa.us>
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk

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