From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
cc: Andres Freund <andres@anarazel.de>, 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: <c00cacaf-7687-17b4-4c8c-25859b28d871@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>
 <20190205060201.jo3ejddklqxb5a4q@alap3.anarazel.de>
 <18071.1549375976@sss.pgh.pa.us>
 <c00cacaf-7687-17b4-4c8c-25859b28d871@postgresql.org>
Comments: In-reply-to "Jonathan S. Katz" <jkatz@postgresql.org>
	message dated "Tue, 05 Feb 2019 09:17:40 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20244.1549378532.1@sss.pgh.pa.us>
Date: Tue, 05 Feb 2019 09:55:32 -0500
Message-ID: <20245.1549378532@sss.pgh.pa.us>
Precedence: bulk

"Jonathan S. Katz" <jkatz@postgresql.org> writes:
> On 2/5/19 9:12 AM, Tom Lane wrote:
>> Anyway, if people want something resembling the old presentation,
>> I think the way to get there is to have some sort of aggregate
>> release notes in a separate place on the web site.  We'd discussed
>> that briefly upthread, but no one's volunteered to push it through.

> I do have one patch for exactly that. Magnus and I disagreed on the
> implementation, perhaps we can circle back around and find something we
> both agree on.

If we do get something like that set up, I'd be inclined to replace
the branch-varying "Prior Releases" text I put into release.sgml
with a single pointer to that.

BTW, while we're thinking about this --- I remembered that as things
stand, we've broken my historical practice of putting up first-draft
minor release notes for people to look at if they choose.  Those will
now be in the newest back branch, which we don't have an automatic
build-and-post pipeline for, AFAIK.  Now, maybe the people who would
review those notes are all comfortable with looking at the git
commitdiff anyway.  But somebody who preferred to wait for the next
guaibasaurus run and then look at the website is now out of luck.
Would it be possible to drive this aggregation off the git copies
of release-NN.sgml (from appropriate branches) instead of the last
released versions?  Or set up something equivalent to the devel
notes pipeline for back branches?

			regards, tom lane