Avoid stuck review if reviewing maintainer becomes unavailable [40011144]

Bug

Status Update

No update yet.

Description

ek...@google.com

created issue #1

Sep 3, 2019 02:04PM

If a maintainer raises an issue in a code review, other maintainers tend to not approve the change until that maintainer ackknowledges that the issue was resolved. If that maintainer gets unavailable (e.g. too busy, out-of-office) the review can get stuck, even if the issue has been addressed by the change owner.

This issue is about finding and implementing ideas that help us avoid this kind of situation.

Comments

ma...@gmail.com <ma...@gmail.com> #2Sep 5, 2019 05:38PM

[Empty comment from Monorail migration]

os...@gmx.de <os...@gmx.de> #3Sep 17, 2019 09:16PM

i suppose you could encourage setting the user status field in a timely manner by making it even easier (e.g., by adding buttons with canned descriptions), or go full big brother on the users (that's what google does, no? :P) and set the status automatically, but other than that it's a purely "cultural" problem ...

ma...@gmail.com <ma...@gmail.com> #4Apr 29, 2021 02:52PM

Community management: making this visible by means of some new dashboard would likely help, overall.

Attention Set is another readily existing feature that helped on this so far, as well.

ek...@google.com <ek...@google.com> #5Jul 15, 2022 08:52AM

[Empty comment from Monorail migration]

is...@google.com <is...@google.com> #6Jul 15, 2022 08:52AM

Edits were made to reflect the following in Monorail: auto-CCs.

Issue 40011144