Code Review Scenario

In progress

1) Reviews should be generic and not necessarily about code so abstract them into general reviews.

2) A review (ReviewX? ) can be created by the owner and assigned to multiple users. ReviewX? could itself be a CM item (task).

Q: If we don't support multiple owners, does this means there is a parent CM item (ReviewX? ) and there are child CM items (ReviewX? -Alex, ReviewX? -Bob, ReviewX? -John) for each of the assignees that are then associated to the parent CM item?

3) Each review assignee creates 0-M review results which could each be CM items but are associated to the parent review CM item.

4) Document reviews typcially start from some kind of document.

Q: Where is this document located? Is it attached to the review CM item? 5) Code R eviews typically start from a change set.

Q: H ow do we associate CM item s to change sets?

-- DenisTyrell - 09 Dec 2009