Patchwork review workflow: archival rules
Paul Zimmermann
Paul.Zimmermann@inria.fr
Tue Nov 16 08:54:10 GMT 2021
Dear Siddhesh,
this sounds good to me.
By the way, do we have an automatic mean to archive patches that are obsolete
because a new version has been posted?
Paul
> Date: Tue, 16 Nov 2021 09:52:58 +0530
> From: Siddhesh Poyarekar <siddhesh@gotplt.org>
>
> Hello,
>
> What do people think about adding the following to the patch review
> workflow[1]? This should help keep the queue under control.
>
> ~~~~~~
> 3. Maintaining your patch queue
>
> 3.1 (existing content)
>
> 3.2. Outdated Patches
>
> To keep tha backlog in patchwork manageable, outdated patches may be
> archived at regular intervals.
>
> * Patches in Changes Requested status will be archived 1 year after
> they have been posted
>
> * Patches older than 3 months that fail to apply to the current main
> branch will be set to Rejected
>
> * Unresolved patches older than 2 years will be archived.
> ~~~~~~
>
> Thanks,
> Siddhesh
>
> [1] https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow
>
More information about the Libc-alpha
mailing list