From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: list of acknowledgments for PG16 |
Date: | 2023-08-22 14:03:29 |
Message-ID: | 952f65b1-8fec-4629-caad-2ba4cd3fec44@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/22/23 09:44, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
>> On 2023-Aug-22, Peter Eisentraut wrote:
>>> The list of acknowledgments for the PG16 release notes has been committed.
>>> It should show up here sometime: <https://www.postgresql.org/docs/16/release-16.html#RELEASE-16-ACKNOWLEDGEMENTS>.
>
>> Hmm, I think these docs would only regenerate during the RC1 release, so
>> it'll be a couple of weeks, unless we manually poke the doc builder.
>
> Yeah. I could produce a new set of tarballs from the v16 branch tip,
> but I don't know the process (nor have the admin permissions) to
> extract the HTML docs and put them on the website.
These days the docs update is part of a scripted process for doing an
entire release.
I'm sure we could figure out how to just release the updated docs, but
with RC1 a week away, is it really worthwhile?
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2023-08-22 14:06:23 | Re: add timing information to pg_upgrade |
Previous Message | torikoshia | 2023-08-22 13:57:07 | Re: Make --help output fit within 80 columns per line |