Re: PostgreSQL 17 Release Management Team & Feature Freeze

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: PostgreSQL 17 Release Management Team & Feature Freeze
Date: 2024-04-08 13:26:09
Message-ID: CA+Tgmoan3F5o4Sk4-8CTCGQDdq4zDg6MX4Wv6gQ9Fw7z8y5BBA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 7, 2024 at 6:50 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> And, as of the moment of typing this email, I get:
> =# select '2024-04-08 00:00-12:00' - now() as time_remaining;
> time_remaining
> -----------------
> 13:10:35.688134
> (1 row)
>
> So there is just a bit more than half a day remaining before the
> feature freeze is in effect.

OK, so feature freeze is now in effect, then.

In the future, let's use GMT for these deadlines. There have got to be
a lot more people who can easily understand when a certain GMT
timestamp falls in their local timezone than there are people who can
easily understand when a certain AOE timestamp falls in their local
timezone.

And maybe we need to think of a way to further mitigate this crush of
last minute commits. e.g. In the last week, you can't have more
feature commits, or more lines of insertions in your commits, than you
did in the prior 3 weeks combined. I don't know. I think this mad rush
of last-minute commits is bad for the project.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2024-04-08 13:29:57 Re: WIP Incremental JSON Parser
Previous Message John Naylor 2024-04-08 13:17:54 Re: [PoC] Improve dead tuple storage for lazy vacuum