| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>, corey(dot)huinker(at)gmail(dot)com |
| Subject: | Re: PG 18 relnotes and RC1 |
| Date: | 2025-09-18 19:32:38 |
| Message-ID: | aMxeVgDW_0pfUBhi@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 18, 2025 at 03:25:08PM -0400, Robert Haas wrote:
> As I see it, while our feature freeze isn't perfect -- mostly because
> too many things get slipped in at the last minute that aren't really
> in great shape -- it's a lot better than the old process where nobody
> really knew what the deadline was. Similarly here, we should just
> agree on some deadline for when the PR and major feature tasks should
> get completed; and if you or whoever don't think you're going to be
> able to make those timelines, then we can either decide on someone
> else to do it or we can decide to move the deadline. Either way, if we
> do that, we're operating by consensus and a shared set of
> expectations.
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.
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2025-09-18 19:35:27 | Re: Updating IPC::Run in CI? |
| Previous Message | Robert Haas | 2025-09-18 19:25:08 | Re: PG 18 relnotes and RC1 |