| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, rmt(at)lists(dot)postgresql(dot)org |
| Subject: | Feature freeze timezone change request |
| Date: | 2026-03-18 23:07:29 |
| Message-ID: | CAGECzQSPzprMNguV6pA671kbSznNmufgqCQGNmpUm4VgdfLW-A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
PS. I love that we're not using AoE anymore[2]
[1]: https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items
[2]: https://www.postgresql.org/message-id/flat/Z_U0fUvVkXOZmRVV%40momjian.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2026-03-18 23:15:29 | Re: remove bits* types |
| Previous Message | Zsolt Parragi | 2026-03-18 23:06:59 | Re: Row pattern recognition |