| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, 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 09:48:36 |
| Message-ID: | 8ba4e905-6045-4b7e-b4f7-4c9e3828ec8f@eisentraut.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 19.03.26 00:07, Jelte Fennema-Nio 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. 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.
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2026-03-19 09:49:24 | Re: Read-only connection mode for AI workflows. |
| Previous Message | Daniel Gustafsson | 2026-03-19 09:45:07 | Re: Serverside SNI support in libpq |