Re: First draft of back-branch release notes is done

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: First draft of back-branch release notes is done
Date: 2019-08-04 16:08:38
Message-ID: 0785e46b-e12d-ef58-6986-76ec7ba66411@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/4/19 10:52 AM, Tom Lane wrote:
> "Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
>> Perhaps instead of "June" it could be the specific version number (which
>> could cause some pain with the back branching?) or the "2019-06-20" release?
>
> Putting in all the version numbers seems like a mess, but specifying
> 2019-06-20 would work --- or we could say "the most recent" minor
> releases?

That or "previous minor release" would seem to work.

(In the PR I'm putting in the versions it was introduced but we have the
luxury of only having one PR.)

Jonathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2019-08-04 16:39:19 Re: First draft of back-branch release notes is done
Previous Message Tom Lane 2019-08-04 15:59:52 Re: A couple of random BF failures in kerberosCheck