Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u2BXZ-00ELE6-AT for pgsql-hackers@arkaria.postgresql.org; Tue, 08 Apr 2025 16:11:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u2BXX-00AyN1-O1 for pgsql-hackers@arkaria.postgresql.org; Tue, 08 Apr 2025 16:11:08 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u2BXX-00AyMs-Ec for pgsql-hackers@lists.postgresql.org; Tue, 08 Apr 2025 16:11:07 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u2BXT-003hon-16 for pgsql-hackers@lists.postgresql.org; Tue, 08 Apr 2025 16:11:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=3TG8LRZxkw4WPz8zBRDjiuZTCRdnnRymiLt/Le1qPiU=; b=sZUuG VN/D5z6Bb6hcrudqAPUGLWgWM/bv60qjQtWxONXfIeP91A7SbpGciXXuJzVQ0ua4l3hY6xMvtiFqe xiqRnP9UKVLDNjEOGM08wVnX1TlkwkO6X3UXOEehHbb8WEF+Wqa5CVe93+v3Qjq++4r1Y23VHZNsY uGNrXCTe+AHQVzrEQPPGQYqZLU6IpppzwOpRb50v4UM6341CKeFbT03voqOF1D3Q+vo7Shkx+PgNF Wwl/93IFsLDms04CshA5j43L8We0uj/OUUxx/f0VDkl3/DSDYdub8T6sCgl2ueclojfB3GyovU4jM K5CYxY4OwUXr9Gx6Yk5d5teMcY2+A==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1u2BXS-003tx4-2F; Tue, 08 Apr 2025 12:11:02 -0400 Date: Tue, 8 Apr 2025 12:11:02 -0400 From: Bruce Momjian To: Peter Eisentraut Cc: PostgreSQL-development Subject: Re: Feature freeze Message-ID: References: <26fb5487-4f74-4a05-8539-d7b860104b64@eisentraut.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26fb5487-4f74-4a05-8539-d7b860104b64@eisentraut.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.