| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Commitfest 2025-03 still has active patches |
| Date: | 2025-07-24 16:58:24 |
| Message-ID: | 202507241658.l4sozjh5ig3k@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2025-Jul-24, Laurenz Albe wrote:
> I just happened to look into https://commitfest.postgresql.org/52/
> and saw plenty of "Active patches" there.
>
> I guess that's a consequence of the new rule established in [1].
I don't know about the rest of it, but I moved all the entries in the
"Bug Fixes" category to the PG19-2 commitfest.
As for the others:
> Are they supposed to stay like that? Should they be closed?
> If yes, "Returned with Feedback"? Or some new state "Abandoned"?
> [1]: https://postgr.es/m/003e3a66-8fcc-4ca0-9e0e-c0afda1c9424%40eisentraut.org
I *think* we should close the Waiting-on-author ones as Returned with
Feedback, and ping the authors of the rest so that each author moves
their patches forward, with a reasonable deadline (two weeks?); we close
patches that aren't moved by then.
Right now we have:
Waiting on author: 14 patches
Needs review: 13 patches
Ready for committer: 4 patches
It's not a lot.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-07-24 17:24:35 | Re: HASH_FIXED_SIZE flag gets lost when attaching to existing hash table |
| Previous Message | Sami Imseih | 2025-07-24 16:52:28 | Re: track generic and custom plans in pg_stat_statements |