public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Jonathan S. Katz <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: [email protected]
Subject: Re: Release note trimming: another modest proposal
Date: Tue, 05 Feb 2019 09:55:32 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<CABUevEzX3dq-uUeMR0mSnCj4B6TK3v4QuQKKsf6Oz+ZdyRHMZg@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

"Jonathan S. Katz" <[email protected]> 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

view thread (58+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Release note trimming: another modest proposal
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox