This isn't a software answer, but if the changes is that large, then we
encourage the author to try and split it into pieces which provide a part of
the whole solution. I.e a review of the server side change, another with all
the database related changes, and a last one with the client side changes.
This helps reviewers with being able to concentrate on the review.
Many studies show that if a review is too large (generally takes more then 1
1/2 hours to go through) then the quality of review comments drop. Reviewing
code requires a high level of concentration and that can only be maintained
for so long.
On Mon, Aug 23, 2010 at 10:51 PM, J Arrizza <cppge...@gmail.com> wrote:
> When initial code is put into RB or a large change is put in, there can be
> many files (say 50). Can't really review that in one sitting so there needs
> to be a way for a reviewer to keep track of which files he's finished with
> (e.g. "ok with file xyz.cpp").
> I see that an issue was raised for this already (by Ben Hollis)
> Issue 1772 <http://code.google.com/p/reviewboard/issues/detail?id=1772>:
> reviewers to check off files they've looked at
> In the meantime, has any one come up with a good workaround? I've thought
> of just putting a comment that says "OK", but that could get messy
> especially with email notifications...
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at