Обсуждение: PostgreSQL 16 Beta 1 release announcement draft

Hi,

Attached is a draft of the release announcement for PostgreSQL 16 Beta 
1. The goal of this announcement is to get people excited about testing 
the beta and highlight many of the new features.

Please review for inaccuracies, omissions, and other suggestions / errors.


Please provide feedback no later than May 24, 0:00 AoE. This will give 
me enough time to incorporate the changes prior to the release the next day.

Thanks,

Jonathan

  2023-05-19 14:18, Jonathan S. Katz wrote:
> Hi,
> 
> Attached is a draft of the release announcement for PostgreSQL 16 Beta
> 1. The goal of this announcement is to get people excited about
> testing the beta and highlight many of the new features.
> 
> Please review for inaccuracies, omissions, and other suggestions / 
> errors.

Would you be ok with capitalising the word "Community" in "PostgreSQL
community" in it?

It's just a subtle emphasis thing, but still... :)

+ Justin

On 2023-05-19 14:18, Jonathan S. Katz wrote:
> Hi,
> 
> Attached is a draft of the release announcement for PostgreSQL 16 Beta
> 1. The goal of this announcement is to get people excited about
> testing the beta and highlight many of the new features.
> 
> Please review for inaccuracies, omissions, and other suggestions / 
> errors.

Typo:

   "PostgreSQL 16 continues to give users to the ability grant privileged 
..."

Should be:

   "PostgreSQL 16 continues to give users the ability to grant privileged 
..."

Hmmm, upon re-reading that whole sentence (not just my fragment of it 
above)
seems pretty unwieldy.  A better one isn't springing to mind though. ;)

---

Should this:

   "Additionally, starting with release, logical replication ..."

Have the word "this" before "release"?

---

Typo:

   "... use the authenticated credentials to connected to other 
services."

Should be:

   "... use the authenticated credentials to connect to other services."

The sentence after that starts:

   "This release also adds ..."

With the one following it starting with "This includes ...".  Together,
they a bit unwieldy too.  Maybe something like this instead?

   "This release also adds several new security-oriented connection
    parameters for clients, including ..."

---

Would this:

   "You can now also set `sslrootcert` to `system` to specify that
    PostgreSQL can use the trusted certificate authority (CA) store
    for that operating system."

Be better as?

   "You can now also set `sslrootcert` to `system` to instruct
    PostgreSQL to use the trusted certificate authority (CA) store
    provided by the operating system."

---

Nothing else is jumping out at me.  It all seems pretty good. :)

+ Justin

Please review for inaccuracies, omissions, and other suggestions / errors.

Minor patch attached, with comments.

---
Cédric Villemain +33 (0)6 20 30 22 52
https://Data-Bene.io
PostgreSQL: Expertise - Formation - Développement - Assistance Technique

On 5/19/23 10:42 AM, Justin Clift wrote:
>   2023-05-19 14:18, Jonathan S. Katz wrote:
>> Hi,
>>
>> Attached is a draft of the release announcement for PostgreSQL 16 Beta
>> 1. The goal of this announcement is to get people excited about
>> testing the beta and highlight many of the new features.
>>
>> Please review for inaccuracies, omissions, and other suggestions / 
>> errors.
> 
> Would you be ok with capitalising the word "Community" in "PostgreSQL
> community" in it?
> 
> It's just a subtle emphasis thing, but still... :)

We don't do this anywhere else on the website or documentation. All the 
other references in the doc just use "community" without "PostgreSQL" so 
if anything we could arguably drop "PostgreSQL" all together there or 
reword the sentence, but I'm not generally inclined to capitalize 
"community" in this context.

Thanks,

Joanthan

On 5/19/23 11:02 AM, Justin Clift wrote:

> The sentence after that starts:
> 
>    "This release also adds ..."
> 
> With the one following it starting with "This includes ...".  Together,
> they a bit unwieldy too.  Maybe something like this instead?

Thanks -- I broke this one up into two sentences.

>    "This release also adds several new security-oriented connection
>     parameters for clients, including ..."
> 
> ---
> 
> Would this:
> 
>    "You can now also set `sslrootcert` to `system` to specify that
>     PostgreSQL can use the trusted certificate authority (CA) store
>     for that operating system."
> 
> Be better as?
> 
>    "You can now also set `sslrootcert` to `system` to instruct
>     PostgreSQL to use the trusted certificate authority (CA) store
>     provided by the operating system."
> 
> ---

I took this suggestion, with modifications.

> Nothing else is jumping out at me.  It all seems pretty good. :)

Thanks!

Hi Cédric,

On 5/20/23 3:24 PM, Cédric Villemain wrote:
> Hi Jonathan,
> 
> 
>> Please review for inaccuracies, omissions, and other suggestions / 
>> errors.
>>
> Minor patch attached, with comments.

Thanks -- for these reviews, it's actually easier just to comment in the 
email vs. attach a patch, as there are multiple feedback providers and 
such the patch may not apply cleanly.

The first two changes had been picked up in previous comments. For the 
last change, I understood where the confusion could come from, so I 
reordered the sentences.

Thanks,

Jonathan

On 5/19/23 12:18 AM, Jonathan S. Katz wrote:
> Hi,
> 
> Attached is a draft of the release announcement for PostgreSQL 16 Beta 
> 1. The goal of this announcement is to get people excited about testing 
> the beta and highlight many of the new features.
> 
> Please review for inaccuracies, omissions, and other suggestions / errors.
> 
> Please provide feedback no later than May 24, 0:00 AoE. This will give 
> me enough time to incorporate the changes prior to the release the next 
> day.

Thanks everyone for your feedback. Here is the updated text that 
combines all of the feedback from both -advocacy and -hackers.

Thanks,

Jonathan

On 2023-05-22 03:06, Jonathan S. Katz wrote:
> On 5/19/23 12:18 AM, Jonathan S. Katz wrote:
>> Hi,
>> 
>> Attached is a draft of the release announcement for PostgreSQL 16 Beta 
>> 1. The goal of this announcement is to get people excited about 
>> testing the beta and highlight many of the new features.
>> 
>> Please review for inaccuracies, omissions, and other suggestions / 
>> errors.
>> 
>> Please provide feedback no later than May 24, 0:00 AoE. This will give 
>> me enough time to incorporate the changes prior to the release the 
>> next day.
> 
> Thanks everyone for your feedback. Here is the updated text that
> combines all of the feedback from both -advocacy and -hackers.

Reading over that, it's pretty good.  Well done. :)

+ Justin