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 1gqmeQ-0005s9-Cs
	for pgsql-docs@arkaria.postgresql.org; Mon, 04 Feb 2019 22:23:38 +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 1gqmeP-0008GZ-4w
	for pgsql-docs@arkaria.postgresql.org; Mon, 04 Feb 2019 22:23:37 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	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 1gqmeO-0008GO-V0
	for pgsql-docs@lists.postgresql.org; Mon, 04 Feb 2019 22:23:36 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1gqmeM-00068a-Ui
	for pgsql-docs@lists.postgresql.org; Mon, 04 Feb 2019 22:23:36 +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 x14MNSm0025040;
	Mon, 4 Feb 2019 17:23:28 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
cc: 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: <856e0ec6-b42a-df70-56ca-f6c5ebf39903@postgresql.org>
References: <19252.1533509841@sss.pgh.pa.us>
 <fa460b8a-e581-ee7c-0118-a89f7b9e1cf9@2ndquadrant.com>
 <CABUevEzX3dq-uUeMR0mSnCj4B6TK3v4QuQKKsf6Oz+ZdyRHMZg@mail.gmail.com>
 <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>
 <402d07a0-227b-71b7-0ecd-0b6c379e3cd0@postgresql.org>
 <18776.1549296730@sss.pgh.pa.us>
 <fd252a70-2ec9-16ad-c58c-e083e77223a7@postgresql.org>
 <31322.1549315549@sss.pgh.pa.us>
 <856e0ec6-b42a-df70-56ca-f6c5ebf39903@postgresql.org>
Comments: In-reply-to "Jonathan S. Katz" <jkatz@postgresql.org>
	message dated "Mon, 04 Feb 2019 17:13:21 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <25038.1549319008.1@sss.pgh.pa.us>
Date: Mon, 04 Feb 2019 17:23:28 -0500
Message-ID: <25039.1549319008@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

"Jonathan S. Katz" <jkatz@postgresql.org> writes:
> On 2/4/19 4:25 PM, Tom Lane wrote:
>> After a bit more thought, I'm inclined to propose that the policy be
>> that we *don't* update the surviving back branches for branch retirement.

> ...so I guess in turn, we would not update back branches with newer
> releases as well, i.e. adding references about 12 to 10? That makes
> sense, and eases some of the burden on releases.

No, I definitely didn't have any intention of putting in forward
references to later releases.  That seems a bit weird.

			regards, tom lane