Patch queue maintenance proposals

Patch queue maintenance proposals

[Siddhesh Poyarekar]

Hi,

I'd like to make the following updates to patch queue management in the 
coming weeks.  I hinted at some of those at the glibc BoF at Cauldron 
but I reckon a proper proposal would be better:

Email commits missing from patchwork to libc-alpha
--------------------------------------------------

Over the last couple of years, about 70% of the patches that were 
committed to the glibc git repo were unmodified and hence found 
corresponding mailing list entries in patchwork.  The 30% have been 
silently ignored so far.  I propose that the script that does this 
checking now should email patches that don't find an entry on patchwork 
to libc-alpha with a [pushed] prefix so that we have an accurate record 
of commits on the mailing list.

Cleaning out outdated patches based on subject line
---------------------------------------------------

I propose that when a patch is being updated as Committed on patchwork, 
the updater also cleans out all patches that have the same subject line 
as the committed patch by setting their state as Superseded. This will 
be based on identical subject line for now, with "v[0-9]\+" filtered out.

Cleaning out patches that fail CI
---------------------------------

Right now, "Fails to Apply" (which was previously "Not Applicable") is a 
terminal state, so it does not stay on the default patch list on 
patchwork.  "Failed CI" patches however stay on the list as action 
requred, probably because we're not always sure if it's a CI bug.  I 
propose that if a patch is marked as "Failed CI", it be archived after 
30 days.

Cleaning out patches with missing DCO or assignment
---------------------------------------------------

I propose that we archive patches with missing DCO or assignment after 1 
year.

Thanks,
Sid

[1] https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow