public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jonathan S. Katz <[email protected]>
To: Andres Freund <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Cc: Michael Banck <[email protected]>
Subject: Re: Release notes for February minor releases
Date: Sun, 6 Feb 2022 14:22:25 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On 2/6/22 1:44 PM, Andres Freund wrote:
> Hi,
>
> On 2022-02-06 13:09:41 -0500, Tom Lane wrote:
>> Andres Freund <[email protected]> writes:
>>> That's obviously to complicated for the release notes. Trying to make it more
>>> understandable I came up with the following, which still does not seem great:
>>> ...
>>
>> How do you like this wording?
>
>> I'm also going to swap the order of this item and the TOAST locking
>> item, since that one is seeming like it's much more relevant to
>> most people.
>
> +1
I'm working on the release announcement and have been following this thread.
Are there steps we can provide to help a user detect that this occurred,
even though it's a low-probability?
Thanks,
Jonathan
Attachments:
[application/pgp-signature] OpenPGP_signature (840B, ../[email protected]/2-OpenPGP_signature)
download
view thread (5+ 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]
Subject: Re: Release notes for February minor releases
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