On Mon, Dec 1, 2025 at 8:28 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Well, if you check your commitfest dashboard [1] you'll see all
> such patches listed under
>
> "Your still open patches in a closed commitfest (you should move or
> close these)"
I did notice that, once Jelte figured out the problem. I wasn't
initially logged in, though. More importantly, I effectively saw
nothing about the problem on the CF entry for the patch in question
(besides, I might have never have thought to look at the dashboard had
I been logged in).
Clearly, if somebody is looking at the CF entry for a patch, they
should always see a prominent "patch needs to be resubmitted" notice
when the patch happens to be in that state. Something right at the
top, that's really hard to miss. It shouldn't matter if they're logged
in or not -- it's very basic information.
Theoretically I could have inferred all this by scrolling down and
noticing that the dozen or so CFs that this patch was submitted to
*doesn't* include the next CF, but evidently that just doesn't work
very well.
> But I agree that some more-active prodding would
> be a good idea. If we send an email nag for your-patch-needs-rebased,
> I don't understand why there's not one for your-patch-just-dropped-
> off-the-radar-and-you-need-to-fix-that.
Right, that seems like the bare minimum.
--
Peter Geoghegan
