public inbox for [email protected]help / color / mirror / Atom feed
Feature freeze timezone change request 11+ messages / 7 participants [nested] [flat]
* Feature freeze timezone change request @ 2026-03-18 23:07 Jelte Fennema-Nio <[email protected]> 0 siblings, 2 replies; 11+ messages in thread From: Jelte Fennema-Nio @ 2026-03-18 23:07 UTC (permalink / raw) To: pgsql-hackers; [email protected] 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 ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Feature freeze timezone change request @ 2026-03-18 23:17 Robert Haas <[email protected]> parent: Jelte Fennema-Nio <[email protected]> 1 sibling, 2 replies; 11+ messages in thread From: Robert Haas @ 2026-03-18 23:17 UTC (permalink / raw) To: Jelte Fennema-Nio <[email protected]>; +Cc: pgsql-hackers; [email protected] On Wed, Mar 18, 2026 at 7:07 PM Jelte Fennema-Nio <[email protected]> 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 ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Feature freeze timezone change request @ 2026-03-19 02:25 Robert Haas <[email protected]> parent: Robert Haas <[email protected]> 1 sibling, 1 reply; 11+ messages in thread From: Robert Haas @ 2026-03-19 02:25 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Jelte Fennema-Nio <[email protected]>; pgsql-hackers; [email protected] On Wed, Mar 18, 2026 at 8:40 PM Tom Lane <[email protected]> wrote: > What we've been using lately for release freezes is noon UTC, which > personally I'd prefer on the grounds that it's not as confusing > which day is meant. Hmm, I kind of like that idea. I don't care that much in the end. But less confusing is better. -- Robert Haas EDB: http://www.enterprisedb.com ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Feature freeze timezone change request @ 2026-03-19 09:48 Peter Eisentraut <[email protected]> parent: Jelte Fennema-Nio <[email protected]> 1 sibling, 1 reply; 11+ messages in thread From: Peter Eisentraut @ 2026-03-19 09:48 UTC (permalink / raw) To: Jelte Fennema-Nio <[email protected]>; pgsql-hackers; [email protected] 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. ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Feature freeze timezone change request @ 2026-03-19 12:28 Jelte Fennema-Nio <[email protected]> parent: Peter Eisentraut <[email protected]> 0 siblings, 1 reply; 11+ messages in thread From: Jelte Fennema-Nio @ 2026-03-19 12:28 UTC (permalink / raw) To: Peter Eisentraut <[email protected]>; +Cc: pgsql-hackers; [email protected] On Thu, 19 Mar 2026 at 10:48, Peter Eisentraut <[email protected]> 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. ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Feature freeze timezone change request @ 2026-03-19 15:07 Andrew Dunstan <[email protected]> parent: Jelte Fennema-Nio <[email protected]> 0 siblings, 0 replies; 11+ messages in thread From: Andrew Dunstan @ 2026-03-19 15:07 UTC (permalink / raw) To: Jelte Fennema-Nio <[email protected]>; Peter Eisentraut <[email protected]>; +Cc: pgsql-hackers; [email protected] On 2026-03-19 Th 8:28 AM, Jelte Fennema-Nio wrote: > On Thu, 19 Mar 2026 at 10:48, Peter Eisentraut <[email protected]> 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 ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Feature freeze timezone change request @ 2026-03-19 15:14 Nathan Bossart <[email protected]> parent: Robert Haas <[email protected]> 0 siblings, 0 replies; 11+ messages in thread From: Nathan Bossart @ 2026-03-19 15:14 UTC (permalink / raw) To: Robert Haas <[email protected]>; +Cc: Tom Lane <[email protected]>; Jelte Fennema-Nio <[email protected]>; pgsql-hackers; [email protected] On Wed, Mar 18, 2026 at 10:25:33PM -0400, Robert Haas wrote: > On Wed, Mar 18, 2026 at 8:40 PM Tom Lane <[email protected]> wrote: >> What we've been using lately for release freezes is noon UTC, which >> personally I'd prefer on the grounds that it's not as confusing >> which day is meant. > > Hmm, I kind of like that idea. I don't care that much in the end. But > less confusing is better. +1 for April 8th, 12:00 UTC. -- nathan ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Feature freeze timezone change request @ 2026-03-19 15:37 Jacob Champion <[email protected]> parent: Robert Haas <[email protected]> 1 sibling, 1 reply; 11+ messages in thread From: Jacob Champion @ 2026-03-19 15:37 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Robert Haas <[email protected]>; Jelte Fennema-Nio <[email protected]>; pgsql-hackers; [email protected] On Wed, Mar 18, 2026 at 5:41 PM Tom Lane <[email protected]> wrote: > I think the UTC-12 business is left over from when we defined it as > AoE, but we're not doing that anymore because it's too confusing. Yeah -- I swapped it recently because I noticed it was still labeled AoE, and I didn't want anyone to have to rediscover last year's thread. It wasn't really meant to be an endorsement for UTC-12. > What we've been using lately for release freezes is noon UTC, which > personally I'd prefer on the grounds that it's not as confusing > which day is meant. +1 for 12:00 UTC. --Jacob ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Feature freeze timezone change request @ 2026-03-19 16:08 Joe Conway <[email protected]> parent: Jacob Champion <[email protected]> 0 siblings, 1 reply; 11+ messages in thread From: Joe Conway @ 2026-03-19 16:08 UTC (permalink / raw) To: Jacob Champion <[email protected]>; Tom Lane <[email protected]>; +Cc: Robert Haas <[email protected]>; Jelte Fennema-Nio <[email protected]>; pgsql-hackers; [email protected] On 3/19/26 11:37, Jacob Champion wrote: > On Wed, Mar 18, 2026 at 5:41 PM Tom Lane <[email protected]> wrote: >> I think the UTC-12 business is left over from when we defined it as >> AoE, but we're not doing that anymore because it's too confusing. > > Yeah -- I swapped it recently because I noticed it was still labeled > AoE, and I didn't want anyone to have to rediscover last year's > thread. It wasn't really meant to be an endorsement for UTC-12. > >> What we've been using lately for release freezes is noon UTC, which >> personally I'd prefer on the grounds that it's not as confusing >> which day is meant. > > +1 for 12:00 UTC. +1 seems reasonable and not likely to be misunderstood -- Joe Conway PostgreSQL Contributors Team Amazon Web Services: https://aws.amazon.com ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Feature freeze timezone change request @ 2026-03-19 18:58 Nathan Bossart <[email protected]> parent: Joe Conway <[email protected]> 0 siblings, 1 reply; 11+ messages in thread From: Nathan Bossart @ 2026-03-19 18:58 UTC (permalink / raw) To: Joe Conway <[email protected]>; +Cc: Jacob Champion <[email protected]>; Tom Lane <[email protected]>; Robert Haas <[email protected]>; Jelte Fennema-Nio <[email protected]>; pgsql-hackers; [email protected] On Thu, Mar 19, 2026 at 12:08:18PM -0400, Joe Conway wrote: > On 3/19/26 11:37, Jacob Champion wrote: >> On Wed, Mar 18, 2026 at 5:41 PM Tom Lane <[email protected]> wrote: >> > What we've been using lately for release freezes is noon UTC, which >> > personally I'd prefer on the grounds that it's not as confusing >> > which day is meant. >> >> +1 for 12:00 UTC. > > +1 seems reasonable and not likely to be misunderstood I updated the wiki page. Shall we also remove the "(tentative)"? -- nathan ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Feature freeze timezone change request @ 2026-03-19 19:06 Jacob Champion <[email protected]> parent: Nathan Bossart <[email protected]> 0 siblings, 0 replies; 11+ messages in thread From: Jacob Champion @ 2026-03-19 19:06 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Nathan Bossart <[email protected]>; Joe Conway <[email protected]>; Robert Haas <[email protected]>; Jelte Fennema-Nio <[email protected]>; pgsql-hackers; [email protected] On Thu, Mar 19, 2026 at 12:03 PM Tom Lane <[email protected]> wrote: > BTW, there is some weird caching issue with that page: I did not see > the up-to-date version, even after multiple refreshes. It wasn't > till I noticed I wasn't logged into the wiki and corrected that > that I saw your edit. I've noticed that with other pages, but I assumed it was intentional/robot-related. --Jacob ^ permalink raw reply [nested|flat] 11+ messages in thread
end of thread, other threads:[~2026-03-19 19:06 UTC | newest] Thread overview: 11+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-03-18 23:07 Feature freeze timezone change request Jelte Fennema-Nio <[email protected]> 2026-03-18 23:17 ` Robert Haas <[email protected]> 2026-03-19 02:25 ` Robert Haas <[email protected]> 2026-03-19 15:14 ` Nathan Bossart <[email protected]> 2026-03-19 15:37 ` Jacob Champion <[email protected]> 2026-03-19 16:08 ` Joe Conway <[email protected]> 2026-03-19 18:58 ` Nathan Bossart <[email protected]> 2026-03-19 19:06 ` Jacob Champion <[email protected]> 2026-03-19 09:48 ` Peter Eisentraut <[email protected]> 2026-03-19 12:28 ` Jelte Fennema-Nio <[email protected]> 2026-03-19 15:07 ` Andrew Dunstan <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox