Gerrit/Code review/Getting reviews

How to get your code reviewed faster
1) Respond to feedback.

Check your Gerrit settings and make sure you're getting email notifications. And if your code fails automated tests, or you got some review already, respond to it in a comment or resubmission, or hit the Abandon button to get your patchset completely off the table while you revise it.

2) Add reviewers.

I try to help with this. If I notice an unreviewed changeset lingering, then I add a review request or two. (These are requests -- there's no way to assign a review to someone in Gerrit.) But it's faster if you do it, right after committing. Some tricks:


 * Click the name of the repository ("Gerrit project"), e.g. operations/debs/squid, and remove "status:open" from the search box to find other changesets in that repository. The people who write and review those changesets would be good candidates to add as reviewers.
 * Search through other commit summaries and changesets. Example: Matmarex and Foxtrott are interested in reviewing frontend changes, so I search for "message:css" to find changesets that mention CSS in their commit summaries to add them to.  You can use this and regexes to find changes that touch the same components you're touching, to find likely reviewers.

3) Review more.

Many eyes make bugs shallow. Read https://www.mediawiki.org/wiki/Code_review_guide and help out with comments, +1, and -1. These numbers are nonbinding, won't cause merges or rejections, and have no formal effect on the code review. But you'll learn, gain reputation, and get people to return the favor by reviewing you in the future. https://www.mediawiki.org/wiki/Git/Tutorial#How_to_comment_on.2C_review.2C_and_merge_code_in_Gerrit has the step-by-step.