From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
cc: "Jonathan S. Katz" <jkatz@postgresql.org>,
        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: <20190125233111.GE13803@momjian.us>
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>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Fri, 25 Jan 2019 18:31:11 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <16079.1548459680.1@sss.pgh.pa.us>
Date: Fri, 25 Jan 2019 18:41:20 -0500
Message-ID: <16080.1548459680@sss.pgh.pa.us>
Precedence: bulk

Bruce Momjian <bruce@momjian.us> writes:
> I assume this means we would only keep the current release notes in the
> git tree too, e.g. 11.0, 11.1, 11.2, etc.

Yeah, I'd imagine that each branch would have just its own release notes.

I'm not sure whether to apply this policy retroactively to the supported
back branches or just establish it going forward.  Maintaining the notes
could be pretty confusing for the next few years if we do the latter,
though.

			regards, tom lane