Changes between Version 35 and Version 36 of PeerReviewPlugin


Ignore:
Timestamp:
Dec 6, 2006, 3:22:25 PM (17 years ago)
Author:
anonymous
Comment:

Comment added

Legend:

Unmodified
Added
Removed
Modified

  • PeerReviewPlugin

    v35 v36  
    8484For peer reviews to be most successful, the actual changes to the files should be highlighted automatically by the revision control system (which the changeset view already does), and allow annotations on the entire file.
    8585
     86==== Comment by anonymous on Thu Dec  7 02:22:25 2006 ====
     87The plugin would be usable for me if:
     88 * I could use diffs of arbitrary revisions and/or paths in the repository (tags, trunk, branches etc.)
     89 * I could also use plain source at specific revision at the same time (like for initial review of old code)
     90 * The commenting process is more like http://gplv3.fsf.org/comments/gplv3-draft-2.html where its indicated which are is a "hot" area and much discuessed. Maybe also with an additional option to have colors not for heat but for age of the latest comment(s)
     91
    8692[[AddComment]]