public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Daniel Gustafsson <[email protected]>
Cc: Peter Geoghegan <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: PG 18 release notes draft committed
Date: Wed, 17 Sep 2025 08:37:51 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CAH2-Wz=2CWXgO1+uyR-VfN3ALMtFnfTtXK-VtkoQQ89ogm=4sg@mail.gmail.com>
<[email protected]>
<CAH2-Wzko57+sT=FcxHHo7jnPLhh35up_5aAvogLtj_D9bATsgQ@mail.gmail.com>
<[email protected]>
<CAH2-Wz=5aGnkPsLH9u1kZED=M8TKvxX2b9XmgdOe+ePO0KxwcQ@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
On Wed, Sep 17, 2025 at 08:30:19AM -0400, Bruce Momjian wrote:
> On Wed, Sep 17, 2025 at 01:07:56PM +0200, Daniel Gustafsson wrote:
> > > On 17 Sep 2025, at 12:58, Bruce Momjian <[email protected]> wrote:
> >
> > > Yes, clearly we need to fix the description we have now. However, we
> > > have already updated this item twice, so I think we need to be careful
> > > to get it right this time:
> >
> > Maybe we should move to a model where the release notes are worked on as a
> > normal docs patch on the list and only committed at around RC1 to keep us from
> > changing and removing from (in case of reverts) documentation published on
> > postgresql.org?
>
> Well, then no one who downloads the software has any visibility on what
> is changed/new, etc? Seems worse than that you are trying to fix.
In addition, we only found out about this mistake because someone read
it and we saw it was wrong. Withholding information only delays us
finding these mistakes.
I frankly don't understand how your suggestion makes anything better.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
view thread (147+ 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]
Subject: Re: PG 18 release notes draft committed
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