Re: PG 18 relnotes and RC1

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>, Peter Eisentraut <peter@eisentraut.org>, Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@lists.postgresql.org>, corey.huinker@gmail.com
Date: 2025-09-18T19:35:34Z
Lists: pgsql-hackers
On Thu, Sep 18, 2025 at 3:32 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
> I think we ought to set a deadline of, say, beta2 or beta3 and have the RMT
> responsible for making sure it happens.  Either of those releases would
> still give us at least a month or so to address feedback before GA, but
> they aren't so early as to require lots of rework due to last-minute
> changes.

That would be fine with me. I'd prefer beta2 -- I think it's really
awkward to try to talk up a forthcoming release when the list of major
features is blank for so long, and I think it's nice to give more
people time to bikeshed the list, too, if anyone is inclined to do
that.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Add list of major features to the v18 release notes.

  2. add_commit_links.pl: error out if missing major version number

  3. doc PG 18 relnotes: Add migration note about tsearch

  4. Remove ts_locale.c's lowerstr()