Re: Feature freeze timezone change request

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, rmt(at)lists(dot)postgresql(dot)org
Subject: Re: Feature freeze timezone change request
Date: 2026-03-19 15:07:27
Message-ID: 9ce749fc-122c-42a2-a60b-23a09fb1362e@dunslane.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2026-03-19 Th 8:28 AM, Jelte Fennema-Nio wrote:
> On Thu, 19 Mar 2026 at 10:48, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>> I don't think the end of the commitfest and feature freeze need to be
>> the same thing. The commitfest might as well end on 31 March or 1 April.
> I think it's fine for the feature freeze to end at a 12:00 UTC instead
> of 0:00 UTC. But I think the commitfest should end after the feature
> freeze, not before. Otherwise patches will show up as committed in
> PG20-1 when in fact they are part of the PG19 release.
>
>

Sure, close it on the 9th some time.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2026-03-19 15:13:50 Re: [PATCH] Optionally record Plan IDs to track plan changes for a query
Previous Message Junwang Zhao 2026-03-19 15:04:58 Re: [PATCH] rewriteGraphTable: Fix missing RTEs in FROM clause by setting inFromCl=true