Changes between Version 20 and Version 21 of PeerReviewPlugin


Ignore:
Timestamp:
May 10, 2006 1:22:16 PM (8 years ago)
Author:
Tim
Comment:

Comment added

Legend:

Unmodified
Added
Removed
Modified
  • PeerReviewPlugin

    v20 v21  
    5050We sure can - see below.  Thanks for the suggestion. 
    5151 
     52==== Comment by Tim on Mi 10 mai 2006 21:22:15 EST ==== 
     53We use Trac and Subversion, but when we do a code review, the author of the code changes sends the source files he changed to other engineers via email, and they place these files into their working directory, and use subversion diff to compare the working directory with the latest source in repository. All of the changes made by the author are then very clear, and comments can be sent back to the author via email, incorporated/discussed, and then new code changes sent out for review. Obviously, this approach works, but would be much better if it was integrated into Trac. Anyway, I have looked at your documentation, and unless I am mistaken you require the code changes to be committed into repository first, then your code is used to mark each line that was changed, and needs to be reviewed. Is this correct ? If so, do you have any plans to store the code changes into a temporary location, and use subvresion diff to compare with the HEAD revision in the repository, so that the changes are very clear to the person reviewing the code ? 
     54 
    5255[[AddComment]]