Help on submission of Code revisions
Posted: Fri 19 Dec 2014 17:04
We are evaluating this tool for organizational deployment.
The help file doesn't really specify how a Author submits a new set of revisions.
It just says "commit to the repository"
So, I'm trying to figure out the steps involved here. We are using TFS and a Pre-commit Check-in policy
Is the correct process:
Author attempts Check-in and is blocked by policy.
Author creates the review (which creates the Shelveset)
Reviewer finds a defect and Rejects the change
Author makes correction on his local workspace file
(These are the steps we don't know)
Does the Author attempt to Check-in again?
Does the Author manually create a new shelveset?
Does the Author "Add revisions" to the Review or does he "Replace Recent Revisions"
These are the steps we don't know)
We're not sure the big difference between Add revision and replace, and when you would use each. And, we're not entirely sure the "most efficient" process for committing the new revision.
The help file doesn't really specify how a Author submits a new set of revisions.
It just says "commit to the repository"
So, I'm trying to figure out the steps involved here. We are using TFS and a Pre-commit Check-in policy
Is the correct process:
Author attempts Check-in and is blocked by policy.
Author creates the review (which creates the Shelveset)
Reviewer finds a defect and Rejects the change
Author makes correction on his local workspace file
(These are the steps we don't know)
Does the Author attempt to Check-in again?
Does the Author manually create a new shelveset?
Does the Author "Add revisions" to the Review or does he "Replace Recent Revisions"
These are the steps we don't know)
We're not sure the big difference between Add revision and replace, and when you would use each. And, we're not entirely sure the "most efficient" process for committing the new revision.