MIME-Version: 1.0
References: <ae4eb804-517d-4811-bfae-bddd1f7b7556@postgresql.org>
In-Reply-To: <ae4eb804-517d-4811-bfae-bddd1f7b7556@postgresql.org>
From: Miaolai Zhou <miaolaizhou@gmail.com>
Date: Tue, 2 Jun 2026 10:36:06 -0400
Message-ID: 
 <CA+w6FA4MO+oxrqb_FO6ujFoT4WRtH039q71Qea=_cD6i9rPyoA@mail.gmail.com>
Subject: Re: PostgreSQL 19 beta 1 release announcement draft
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: PostgreSQL Advocacy <pgsql-advocacy@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2Bw6FA4MO%2Boxrqb_FO6ujFoT4WRtH039q71Qea%3D_cD6i9rPyoA%40mail.gmail.com>
Precedence: bulk

Thanks you, Jonathan! Here's my feedback:

1. Broken link: The PostgreSQL 19 docs link
(https://www.postgresql.org/docs/19/release-19.html) is showing "Page
not found".

2. Move the call-to-action up: I'd suggest moving "Testing for Bugs &
Compatibility" closer to the top of the announcement. Since many
readers don't make it to the end, we might lose them before they see
how they can help. We could then echo it again at the end to reinforce
how valuable community testing is.

3. Consider adding a feature summary table: What do you think about
including a table that lists the key features with one-line summaries,
then linking to the detailed paragraphs? It would add some length, but
it could help readers quickly scan and jump to what interests them
most.

Thanks,

Miaolai (Mila) Zhou

On Thu, May 28, 2026 at 11:23=E2=80=AFPM Jonathan S. Katz <jkatz@postgresql=
.org> wrote:
>
> Hi,
>
> Attached is the draft of the PostgreSQL 19 Beta 1 release announcement.
> Please review for accuracy (e.g. are features described correctly? Did I
> miss a revert), recommendations on additions or glaring omissions,
> structure, etc.
>
> Please provide feedback no later than June 4, 2026 12:00 UTC (though
> preferably earlier!)
>
> Thanks,
>
> Jonathan