| 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:39:19 |
| Message-ID: | d9aaf5ca-3560-c2f2-ea09-0c49c33f6f09@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/4/19 11:08 AM, Jonathan S. Katz wrote:
> 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.)
Attached is the first draft of the PR.
Jonathan
| Attachment | Content-Type | Size |
|---|---|---|
| 20190808updaterelease.md | text/markdown | 6.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2019-08-04 17:30:04 | Re: pglz performance |
| Previous Message | Jonathan S. Katz | 2019-08-04 16:08:38 | Re: First draft of back-branch release notes is done |