From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Chapman Flack <chap(at)anastigmatix(dot)net>, Noah Misch <noah(at)leadboat(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: 2021-02-11 release announcement draft |
Date: | 2021-02-10 15:39:48 |
Message-ID: | 6f396d7d-029b-7551-82fb-6e1cdfee3ab4@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/10/21 10:19 AM, Chapman Flack wrote:
> On 02/10/21 10:15, Jonathan S. Katz wrote:
>> On 2/8/21 6:11 PM, Noah Misch wrote:
>>> On Mon, Feb 08, 2021 at 05:40:41PM -0500, Jonathan S. Katz wrote:
>>>> Some of these issues only affect version 13, but may also apply to other
>>>> supported versions.
>>>
>>> Did you want s/may/many/?
>>
>> Nope. The bugs may also apply to other versions. Maybe to be clearer
>> I'll /may/could/?
>
> If that's what was intended, shouldn't it be "but others may also apply
> to other supported versions"? ^^^^^^
>
> Surely the ones that "only affect version 13" do not affect other versions,
> not even on a 'may' or 'could' basis.
The main goals of the release announcement are to:
* Let people know there are update releases for supported versions that
fix bugs.
* Provide a glimpse at what is fixed so the reader can determine their
level of urgency around updating.
* Direct people on where to download and find out more specifics about
the releases.
I appreciate the suggestions on this sentence, but I don't think the
desired goals hinges on this one word.
Thanks,
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2021-02-10 15:43:42 | Re: 2021-02-11 release announcement draft |
Previous Message | Michael Banck | 2021-02-10 15:36:13 | Re: 2021-02-11 release announcement draft |