From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: GNU C Library <libc-alpha@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>
Subject: Patch queue maintenance proposals
Date: Mon, 19 Sep 2022 09:50:20 -0400 [thread overview]
Message-ID: <c9566eb6-a9d7-3cd2-b9c6-16d52bf62183@gotplt.org> (raw)
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
reply other threads:[~2022-09-19 13:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c9566eb6-a9d7-3cd2-b9c6-16d52bf62183@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).