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: <20190205171707.3ct4ch3q25xg4lpo@alap3.anarazel.de>
References: <cbd4aeb5-2d9c-8b84-e968-9e09393d4c83@postgresql.org>
 <20190125233111.GE13803@momjian.us> <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>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Tue, 05 Feb 2019 09:17:07 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <10392.1549387440.1@sss.pgh.pa.us>
Date: Tue, 05 Feb 2019 12:24:00 -0500
Message-ID: <10393.1549387440@sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> On 2019-02-05 12:10:57 -0500, Tom Lane wrote:
>> For something like release-9-6-10.html, there's no value in having it
>> appear in three or four different places.  You can't even argue that
>> the later branches might be more up-to-date: that text is *the same*,
>> modulo toolchain-forced markup differences, in every branch; or at
>> least if it isn't it means I screwed up.

> If somebody proposed adding automatic redirects from the older linked
> versions to the newest /current/ URL with that version's release notes,
> I'm not sure I would have argued against that.  But I do *not* think
> it's actually accurate they are the same - it's a significant difference
> that they're linking to the corresponding version's pages, because those
> will contain that version's syntax / docs.

Huh?  The release note contents are identical cross-branch.
I know, because I'm generally the one making them.

Anyway, what I'm now thinkimg would be useful would be to set up a
separate area for aggregated release notes, driven off a new git
repo as I suggested; and then we could consider auto-redirecting
existing URLs like
https://www.postgresql.org/docs/10/release-9-4-19.html
into that area.

			regards, tom lane