On 08/04/2025 19:11, Bruce Momjian wrote:
On Tue, Apr 8, 2025 at 06:00:27PM +0200, Peter Eisentraut wrote:
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.
Well, they kind of did this by saying midnight on April 8 AoE, rather
than end-of-day in April 7 AoE. Actually, I had originally said April 8
AoE and then was told I had to specify a time --- maybe the time was the
mistake, and we still have April 8 to add features. ;-)
At the end of the day (pun not intended), it doesn't matter much.
Nothing special happens when the feature freeze begins. If some
committers interpret it a little differently, it doesn't matter.
That said, +1 for using UTC in the future for clarity.
- Heikki
