Re: PostgreSQL 17 Release Management Team & Feature Freeze

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, 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 14:42:05
Message-ID: 74da16cecabc204805afc5b0bb94767c78e9be22.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2024-04-08 at 09:26 -0400, Robert Haas wrote:
> 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.

I found that there are a lot of people who can only get going with a
pressing deadline. But that's just an observation, not an excuse.

I don't know if additional rules will achieve anything here. This can
only improve with buy-in from the committers, and that cannot be forced.

Yours,
Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey M. Borodin 2024-04-08 14:42:39 Re: PostgreSQL 17 Release Management Team & Feature Freeze
Previous Message Robert Treat 2024-04-08 14:41:17 Re: PostgreSQL 17 Release Management Team & Feature Freeze