post-commit code review workflow
I have a team of developers all committing to the same development cvs branch. Then we have the code review person load up all changes in code collaborator for review; but, it appears that there's no...
Forum Discussion
Hi Tom,
As these are post-commit reviews, I'm assuming you're using "addcvsdiffs"?
This appears to be a process issue, and outside of using CVS' "blame" feature, I don't know that you can get the information you're looking for.
Internally, we use Git and do pre-commit reviews - verifying work independently. I'd love to tell you that switching to Git will solve your problems, but the best way to get the information you seem to be looking for is to do pre-commit reviews.
I hope that helps.
As these are post-commit reviews, I'm assuming you're using "addcvsdiffs"?
This appears to be a process issue, and outside of using CVS' "blame" feature, I don't know that you can get the information you're looking for.
Internally, we use Git and do pre-commit reviews - verifying work independently. I'd love to tell you that switching to Git will solve your problems, but the best way to get the information you seem to be looking for is to do pre-commit reviews.
I hope that helps.
