Re: Feature freeze

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Feature freeze
Date: 2025-04-08 16:11:02
Message-ID: Z_VKlgHax--cF8CV@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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. ;-)

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2025-04-08 16:13:28 Re: Horribly slow pg_upgrade performance with many Large Objects
Previous Message Melanie Plageman 2025-04-08 16:06:47 Finalizing read stream users' flag choices