This is the mail archive of the
mailing list for the glibc project.
Suggest "Dropped" state for patchwork.
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>, Siddhesh Poyarekar <siddhesh at redhat dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Fri, 28 Nov 2014 13:09:37 -0500
- Subject: Suggest "Dropped" state for patchwork.
- Authentication-results: sourceware.org; auth=none
While doing more and more patcwork work I noticed a problem
I had with the `Rejected` state.
The more rejected patches you have the harder it becomes to
review the rejected patch list to see which patches you want
to do over again with a different approach.
I have updated "Patch Review Workflow" with a "Dropped"
state that developers can use to indicate they don't plan
to do any more work on the patch. Either "Rejected" or
"Dropped" are end states, but "Dropped" allows the developer
to also use patchwork as a todo list, not just the maintainers.
And as maintainers we all have our own patches to track.
https://sourceware.org/glibc/wiki/Patch Review Workflow
Should we add a "Dropped" state?