Re: Feature freeze timezone change request - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Feature freeze timezone change request
Date
Msg-id CA+Tgmoboa1ce6EKgD2DH-=Q1P0Uux7dV7rqedYH1EB6ey=03SQ@mail.gmail.com
Whole thread
In response to Feature freeze timezone change request  (Jelte Fennema-Nio <postgres@jeltef.nl>)
Responses Re: Feature freeze timezone change request
List pgsql-hackers
On Wed, Mar 18, 2026 at 7:07 PM Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
> I was notified that the tentative feature freeze timestamp is on the
> wiki[1] as: April 8, 2026 0:00 UTC-12
>
> I request that the final feature freeze timestamp be set to 0:00 UTC,
> not 0:00 UTC-12.

+1.

> The comitfest app currently only supports dates as
> the start/end of a commitfest, not datetimes. By using 0:00 UTC I (or
> anyone else with admin access) can simply fill in the last day of the
> commitfest, and the commitfest will be automatically closed when that
> day ends in UTC.

But not for this reason. It would be fine if the CF app closed the CF
twelve hours before or after the actual feature freeze. But using UTC
for everything is way less confusing, IMHO.

> PS. I love that we're not using AoE anymore[2]

+1

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: remove bits* types
Next
From: Robert Haas
Date:
Subject: Re: pgsql: Don't leave behind files in src dir in 007_multixact_conversion.