From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz>, Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: new commitfest transition guidance |
Date: | 2025-02-27 12:27:24 |
Message-ID: | b3ed38dd-ee8e-4e6c-8452-42bd19b727ef@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2025-02-27 Th 12:16 AM, Michael Paquier wrote:
> On Mon, Feb 03, 2025 at 12:22:52PM +0100, Peter Eisentraut wrote:
>> CF 2025-01 has just ended, so I suggest that everyone try this now. We can
>> check in perhaps two weeks whether this results in lots of stuff falling
>> through the cracks or still too much stuff with unclear status being moved
>> forward, and then see what that might mean going forward.
> CF 2025-03 is to begin in more or less 48 hours, and we have still a
> grand total of 72 patches still listed in CF 2025-01:
> https://commitfest.postgresql.org/51/
>
> It's a good score, as 286 patches have been moved without doing any
> kind of massive bulky and manual vacuum work on all these entries.
>
> As these have not been moved by their respective authors and/or
> reviewers, perhaps, based on the guidance I am reading from this
> thread, it would be time to give up on these rather than move them
> around?
There are 4 marked "Ready For Committer" - all authored by committers :-)
Maybe the message isn't getting through, After I got the email message,
I moved one yesterday that I am listed on as an author although I'm not
really, but the real author had not moved.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2025-02-27 12:43:50 | Re: SQLFunctionCache and generic plans |
Previous Message | Alexander Pyhalov | 2025-02-27 12:25:03 | Re: SQLFunctionCache and generic plans |