| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | 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 05:16:55 |
| Message-ID: | Z7_1R3eLSVCiOwFS@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2025-02-27 05:38:32 | Re: Improve CRC32C performance on SSE4.2 |
| Previous Message | Masahiko Sawada | 2025-02-27 05:16:22 | Re: Restrict copying of invalidated replication slots |