From 8671000ff712106b66ed6cba5024c767ca981a5b Mon Sep 17 00:00:00 2001 From: Manish V Badarkhe Date: Wed, 5 Jul 2023 00:25:08 +0100 Subject: [PATCH] docs: add guidelines for abandoning patches The code review guidelines have been updated to explain when patches that do not receive a response to the review comments will be abandoned. Change-Id: I60539e16ca41245cf1b352f24557be1b3c67c367 Signed-off-by: Manish V Badarkhe --- docs/process/code-review-guidelines.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/process/code-review-guidelines.rst b/docs/process/code-review-guidelines.rst index ccdd110e1..bd4281132 100644 --- a/docs/process/code-review-guidelines.rst +++ b/docs/process/code-review-guidelines.rst @@ -94,6 +94,14 @@ contributor you are expected to: directory to have the freedom to change it in any way. This way, your changes benefit everyone and will be maintained over time. +- It is the patch-author's responsibility to respond to review comments within + 21 days. In the event that the patch-author does not respond within this + timeframe, the maintainer is entitled to abandon the patch(es). + Patch author(s) may be busy with other priorities, causing a delay in + responding to active review comments after posting patch(es). In such a + situation, if the author's patch(es) is/are abandoned, they can restore + their work for review by resolving comments, merge-conflicts, and revising + their original submissions. Guidelines for all reviewers ----------------------------