Re: PG 18 relnotes and RC1
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-development <pgsql-hackers@lists.postgresql.org>,
Peter Eisentraut <peter@eisentraut.org>
Date: 2025-08-30T16:52:45Z
Lists: 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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add list of major features to the v18 release notes.
- b585f25284d2 18.0 landed
-
add_commit_links.pl: error out if missing major version number
- 0c6d572c1173 19 (unreleased) landed
-
doc PG 18 relnotes: Add migration note about tsearch
- d1073c3b4cc8 18.0 cited
-
Remove ts_locale.c's lowerstr()
- fb1a18810f07 18.0 cited