From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Release note trimming: another modest proposal
In-reply-to: <fa460b8a-e581-ee7c-0118-a89f7b9e1cf9@2ndquadrant.com>
References: <19252.1533509841@sss.pgh.pa.us>
 <fa460b8a-e581-ee7c-0118-a89f7b9e1cf9@2ndquadrant.com>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
	message dated "Fri, 10 Aug 2018 01:38:43 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4816.1533858308.1@sss.pgh.pa.us>
Date: Thu, 09 Aug 2018 19:45:08 -0400
Message-ID: <4817.1533858308@sss.pgh.pa.us>
Precedence: bulk

Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 06/08/2018 00:57, Tom Lane wrote:
>> Anyway, I'd like to propose a compromise position that I don't think
>> has been discussed before: let's drop release notes for branches
>> that were already EOL when a given branch was released.

> Why not go further and just ship the release notes of the current major
> version.  If you want to look at the release notes of version 11, read
> the documentation for version 11.  Who reads the documentation of
> version 12 to get the release notes of version 11?

Personally, I'd be OK with that, but it seemed to me that that had
already been proposed and shot down (on the grounds of not-enough-
history) the last time this was discussed.

			regards, tom lane