Patchwork

We use patchwork to manage the different patches sent on the mailing list: https://patchwork.kernel.org/project/mptcp/

Status

• New → Waiting for review for anybody
• Under review → In review or waiting for precisions
• Accepted → applied
• Rejected → we don't want that (at all)
• RFC → RFC (be careful, no more an "Action Required" state)
• Not applicable → to be rebased
• Changes requested → we need a new version (be careful, no more an "Action Required" state)
• Awaiting Upstream → waiting to be applied (be careful, no more an "Action Required" state)
• Superseded → replaced by another one? Very similar to "Changes requested", we don't have to use it
• Deferred → for later (be careful, no more an "Action Required" state)
• Needs review/ACKs → When assigned to something but the review didn't start → we can also keep the "Under review" status

Archive

We do that after each weekly meeting to be able to discuss about what has recently been changed.