From: Bruce Momjian <bruce@momjian.us>
To: jian he <jian.universality@gmail.com>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>
Cc: Marcos Pegoraro <marcos@f10.com.br>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Daniel Gustafsson <daniel@yesql.se>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Detailed release notes
Date: Wed, 11 Sep 2024 10:16:04 -0400
Message-ID: <ZuGmJPB2P9oaqF8N@momjian.us> (raw)
In-Reply-To: <CACJufxF+9YCDce5vzmZY6ZCEeTJsYFG-kPohT9UjKikJX30mGw@mail.gmail.com>
References: <F8C2CC64-5265-4668-901D-B4A20420EC89@yesql.se>
<CAB-JLwYDP58XRTjQFGswBEBHokWSh00NbvFAsAVzSQgDr+hMFg@mail.gmail.com>
<4D1ACBCD-70AD-4286-8640-6DFC2ED206B8@yesql.se>
<1673965.1722003082@sss.pgh.pa.us>
<ZsPC8FoTFeW9PP0n@momjian.us>
<CAB-JLwY8hJ=N4G_kePkkR87CdQdAkL9MDAgFwP+WM7_dP7MgOQ@mail.gmail.com>
<2043874.1724347651@sss.pgh.pa.us>
<CAB-JLwbX-P3_c+FS=FgPrAPMojpTZEno6eQnDg1Aa7zWtOqyng@mail.gmail.com>
<CAGECzQRoz1dqyBc+0M48tzwYDbO-hYbXyVN8_AH9rfO436unqA@mail.gmail.com>
<CACJufxF+9YCDce5vzmZY6ZCEeTJsYFG-kPohT9UjKikJX30mGw@mail.gmail.com>
On Sat, Sep 7, 2024 at 10:12:00AM +0800, jian he wrote:
> On Sat, Sep 7, 2024 at 6:30 AM Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
> >
> > On Thu, 22 Aug 2024 at 21:34, Marcos Pegoraro <marcos@f10.com.br> wrote:
> > > I understand your point, and agree with that for previous releases, but since we have a month only for version 17, will this process work properly until that date ?
> > > I think a release notes is more read as soon as it is available than other months, isn't it ?
> > > And this feature is just a HTML page, so if it's done manually or automatically, from the reader point of view it'll be exactly the same.
> >
> > Big +1 to this. It would definitely be great if we would have these
> > commit links for previous release notes. But the PG17 GA release is
> > probably happening in 19 days on September 26th. I feel like we should
> > focus on getting the manual improvements from Jian He merged,
> > otherwise we'll end up with release notes for PG17 on release day that
> > are significantly less useful than they could have been. Let's not
> > make perfect the enemy of good here.
> >
>
> hi. Thanks for your interest.
> patch updated.
>
>
> I have proof-read release-17.sgml again,
> making sure the commit url's commit is the same as
> release-17.sgml comment's git commit.
I will write a script to do this, but I am not sure I will have it done
by the time we release Postgres 17.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
When a patient asks the doctor, "Am I going to die?", he means
"Am I going to die soon?"
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: pgsql-hackers@postgresql.org
Cc: bruce@momjian.us, jian.universality@gmail.com, postgres@jeltef.nl, marcos@f10.com.br, tgl@sss.pgh.pa.us, daniel@yesql.se
Subject: Re: Detailed release notes
In-Reply-To: <ZuGmJPB2P9oaqF8N@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox