RTC를 이용한 Code Review Process

Project configuration

• Precondition : "Require Work Item Approval" 
• for "Deliver (client)" operation 
• for "Everyone" role. 
• In the "Required approvals", for the "Review" type, at least one from "Everyone" role (or "Team Member" role) is set. 
• "User may overrule" may also be checked if not all code delivery may require a review process. 

Scenario
There are three developers - D1, D2 & D3 - all using RTC Eclipse client.

1. D1 does the code change for files f1 & f2 in her local workspace and saves them. f1 and f2 appears as unresolved in the pending changes view. 
2. D1 checks-in f1 & f2 into a new change set "CS". 
3. Right clicks on "CS" and select "Submit for Review" menu option and associate to a WI (existing or a new one) and select approvers - D2 as the approver for f1 review (subject field is used to tell what to review) and D3 as approver for f2 review. 
4. The approval/Review process will be in the pending state. 
5. D2 & D3 gets intimation of the review task assigned to them through a query - "Pending approvals for me". 
6. D2 opens the WI and in the Links section, double clicks on the f1 in the change set and see the diff in the Change Explorer. Does the review. Optionally, adds comment for D1 in the discussion field of the WI. Changes the Review approval state from pending to approved. 
7. D3 follows the same process as D2 but rejects because the f3 code change is not acceptable. Changes the Review approval state from pending to rejected. 
8. D1 gets the review comment via email/feed - because D1 is the owner and the subscriber of the WI. 
9. D1 fixes the code in f2 based on D3's review and checks in to the same changeset. 
10. D1 adds D3 again for the new review approval in the same WI. 
11. D3 gets intimation of the review task assigned to him through a query - "Pending approvals for me". 
12. D3 opens the WI and in the Links section, double clicks on the f2 in the changeset and see the diff in the Change Explorer. Does the review. Optionally, adds comment for D1 in the discussion field of the WI. Changes the Review approval state from pending to approved. 
13. D1 gets the review comment via email/feed - because D1 is the owner and the subscriber of the WI. 
14. D1 delivers the changeset (or invokes "Complete" action on the changeset) because all the approvals in the WI are in approved state. 
15. The complete history of the code review process (rejected ones, approved ones) are in the "Approvals" tab.

제안 https://jazz.net/wiki/bin/view/Main/SCMChangeSetReview
-