Re: PG 18 relnotes and RC1 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PG 18 relnotes and RC1
Date
Msg-id 16021.1756572765@sss.pgh.pa.us
Whole thread Raw
In response to PG 18 relnotes and RC1  (Bruce Momjian <bruce@momjian.us>)
Responses Re: PG 18 relnotes and RC1
Re: PG 18 relnotes and RC1
Re: PG 18 relnotes and RC1
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Second, the release note item added by this commit:
>     commit d1073c3b4cc
>     Author: Peter Eisentraut <peter@eisentraut.org>
>     Date:   Fri Aug 29 10:18:10 2025 +0200

> Unfortunately src/tools/add_commit_links.pl can't process the <ulink>
> and throws an error because the previous line does not end with a
> parenthesis.  If I add "()" after the last line in the text block, it
> works fine, but obviously this is not acceptable.

I suppose that the expectation is that every release note item
will be credited to someone.  Why does this item lack a credit?

If we're okay with items not having credits, then
add_commit_links.pl's logic for where to put the <ulink>s needs
improvement.  I don't really understand why it's looking for
parens in the first place -- why isn't the rule simply "put them
before the first </para> in the item"?

In either case, I don't agree with hacky workarounds like manually
munged ulink entries ...

> I can commit this once our RC1 git tree freeze is over.  Is that Tuesday?

The release freeze doesn't apply to the release notes ;-)

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Add error_on_null() to produce an error if the input is null
Next
From: Arseniy Mukhin
Date:
Subject: Move block_range_read_stream_cb batchmode comment