Re: new commitfest transition guidance - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: new commitfest transition guidance
Date
Msg-id CAH2-WzmjoXAJmovkaRNHKA1YcAaqFpebbVjkUExmQ_wzVPvdRg@mail.gmail.com
Whole thread Raw
In response to Re: new commitfest transition guidance  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: new commitfest transition guidance
Re: new commitfest transition guidance
List pgsql-hackers
On Tue, Feb 4, 2025 at 8:10 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> As of right now, I see that 79 CF entries have been manually pushed to
> 2025-03 (but it's hard to tell how many of those were moved before
> 2025-01 closed).  180 live entries are still in 2025-01, including
> 20 RfC ones.  I think this experiment is already proving to be a
> failure, and if you increase the cost of compliance substantially,
> people just won't do it at all.

Evidently this new policy is why my skip scan patch series wasn't
being tested by CI.

I just don't think that this new policy makes sense. At least not as
implemented. Do we all now need to set ourselves reminders to re-enter
patches to each CF, lest we be accused of abandoning patches due to a
lack of interest?

--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: Better visualization of default values
Next
From: Tom Lane
Date:
Subject: Re: new commitfest transition guidance