The review stage is a very important part in the development process. Following are some of the reasons this stage is important:
Everyone is encourages to review code. You don’t need to know every detail of the code base. You need to understand only what the code related to the fix does.
Go to review.openstack.org and filter by Open Zaqar fixes. Select a fix from the list to review. Try to select an easy patch for your first review. That will help you to gain some confidence. Download the patch to your local repository and test it:
$ git review -d [review-id]
The review-id is the number in the URL (check the screenshot for more details).
Example:
$ git review -d 92979
This git command creates a branch with the author’s name and enables you to test the patch in your local environment.
Inspect the code. Use all of the best programming practices you know as you review the code.
Do you consider that some code should be better located in another place within the file, or maybe in another file? If so, suggest this in the review comment and score with a -1 if you think that it’s that important.
Do you think that the code structure could be improved? Keep the DRY, YAGNI and KISS principles in mind.
Give grammar and orthography feedback. Many of our contributors are not native English speakers, so it is common to find some errors of this type.
Make sure that:
Check Git Commit Messages for more information on how you should write a git commit message.
The coding style matches guidelines given in HACKING.rst.
You might need to split some patches to improve cohesion and/or reduce size.
The patch does what the commit message promises.
Unit and functional tests are included and/or updated.
If during the inspection you see a specific line you would like to bring up to discussion in the final review, leave feedback as an inline comment in Gerrit. This will make the review process easier. You can also use prefixes described in Reviewer Guide for Zaqar inline comments.
Keep in mind the Reviewer Guide and be respectful when leaving feedback.
Hit the Review button in the web UI to publish your comments and assign a score.
Things to consider when leaving a score:
Remember to leave any comment that you think is important in the comment form. When you are done, click Publish Comments.
For more details on how to do a review, check out the Gerrit Workflow Review section document.