Today, we're going to look at starting a code review. Code reviews are collections of files, in specific file versions, with assigned reviewers. Reviewers can add comments to the files being reviewed. Every code review has at least one author. The author is the person responsible for the review, making sure comments are addressed. Authors can also add comments and we'll see later can also edit comments of others. Once you've created a code review and added files to it, it's time to start the review process. If you haven't already done this, open up the code review window and select the review you want to start and click the “Start Code Review” button.
In order to start, you must have at least one reviewer assigned. The notes here are about this particular round of reviews. These are separate from the notes we added when initially creating the review to help your reviewers understand what they were looking at or specific areas or concepts you want feedback on. Once you have your reviewers assigned, you can pick a due date for feedback, then click the start review button. Each reviewer will receive an email letting them know the code review name, authors, and any notes you've added. When you start the review, it enters the awaiting review state.
When a reviewer receives an email notifying them they have a code review, they can open Surround SCM and bring up the code review window. By default, this window opens showing any unapproved code reviews that you are the author of. By changing the filter to unapproved reviews assigned to me, you can see the outstanding code reviews that others have made you the reviewer of. We'll look at how reviewers add comments and move a code review through its workflow in another video. Thanks for watching.