Date: Tue, 5 Feb 2019 09:28:17 -0800
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
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
Message-ID: <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <10393.1549387440@sss.pgh.pa.us>
Precedence: bulk

Hi,

On 2019-02-05 12:24:00 -0500, Tom Lane wrote:
> 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.

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. Even when the contents of the specific release-*.html page look
the same, the pages they link to will differ more.  As I said, that's
not necessarily bad, but that did use to be a difference between the
pages depending on which version they are from.

Greetings,

Andres Freund