From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Feature freeze |
Date: | 2025-04-08 16:00:27 |
Message-ID: | 26fb5487-4f74-4a05-8539-d7b860104b64@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08.04.25 16:59, Bruce Momjian wrote:
> On Tue, Apr 8, 2025 at 10:36:45AM -0400, Bruce Momjian wrote:
>> Since we recorded feature freeze as April 8, 2025 0:00 AoE (anywhere on
>> Earth):
>>
>> https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items#Important_Dates
>> https://www.timeanddate.com/time/zones/aoe
>>
>> and it is now 2:34 AM AoE, I guess we are now in feature freeze.
>
> Frankly, I think the name "anywhere on Earth" is confusing, since it
> really is "everywhere on Earth":
>
> https://en.wikipedia.org/wiki/Anywhere_on_Earth
>
> Anywhere on Earth (AoE) is a calendar designation that indicates
> that a period expires when the date passes everywhere on Earth.
Yes, that works intuitively when you specify that sometimes ends when a
certain day ends, for example:
"The feature development phase ends at the end of day of April 7, AoE."
That means, everyone everywhere can just look up at their clock and see,
it's still April 7, it's still going. (Of course, others can then do
the analysis and keep going until some time on April 8, but that would
be sort of against the spirit.)
If you use it as a time zone with a time of day, it doesn't make
intuitive sense.
From | Date | Subject | |
---|---|---|---|
Next Message | Wolfgang Walther | 2025-04-08 16:01:42 | Re: [PoC] Federated Authn/z with OAUTHBEARER |
Previous Message | Nathan Bossart | 2025-04-08 15:59:09 | Re: prevent 006_transfer_modes.pl from leaving files behind |