summaryrefslogtreecommitdiff
path: root/doc/development/code_review.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/development/code_review.md')
-rw-r--r--doc/development/code_review.md9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/development/code_review.md b/doc/development/code_review.md
index f45de25aee5..e38aad55afa 100644
--- a/doc/development/code_review.md
+++ b/doc/development/code_review.md
@@ -134,10 +134,11 @@ as the maintainer to ultimately approve and merge it.
Try to review in a timely manner; doing so allows everyone involved in the merge
request to iterate faster as the context is fresh in memory. Further, this
-improves contributors' experiences significantly. Provided full availability;
-reviewing within two work days should be the aim. If you don't think you'll be
-able to review a merge request within that time, let the author know as soon as
-possible.
+improves contributors' experiences significantly. Reviewers should aim to review
+within two working days from the date they were assigned the merge request. If
+you don't think you'll be able to review a merge request within that time, let
+the author know as soon as possible. When the author of the merge request has not
+heard anything after two days, a new reviewer should be assigned.
Maintainers should check before merging if the merge request is approved by the
required approvers.