> Maybe a reviewer should have two responsibilities: [...]
For code review: you can make lots of different choices for responsibilities and still have a good code review process. It just needs to fit your goals and people in your organisation should be on the same page about it.
So for example for code review, I don't think the reviewer should try very hard to understand the change. Explaining the change so that it is easy to understand is one of the responsibilities of the author who proposes the change.
Similarly it's upon the author to demonstrate that the proposed change doesn't introduce any defects and to explain how it meets all criteria. It's not on the reviewer to go bug hunting.
That is so that the next guy who view the change in a few years in version control history to understand how the software developed (or how a bug was introduced) has a fighting chance to understand what happened from what was preserved in version control alone.
Not that it matters, because they don’t have the time to manually review source code changes either. At best there’s likely some automated static analysis for undocumented API symbols and common malware signatures.
And vice versa. ;-)
This reminds me of code review in general. Some reviewers have the etiquette of "if it was there already, then it's outside the scope of this review," and some don't.
Maybe a reviewer should have two responsibilities:
1. Review the proposed _change_ and verify that it meets all criteria and doesn't introduce defects.
2. Make note of any existing defects, which are then recorded.
Maybe an app developer can be required to resolve everything found in (2) before the _next_ review.
I've never released an app before.