|Version 21 (modified by Tim, 10 years ago) (diff)|
Distributed Peer Review Plugin
If you have any issues, create a new ticket.
04/25/2006 - This is our v1.0 release. We've successfully completed testing and fixed every bug we found. We added some screenshots to the page (bottom), so you can check out some sample screens from our plugin.
04/07/2006 - This update should fix almost all the problems. We've done extensive testing and everything should be stable. We've got some great bugs from the community and we think we've fixed them all. Right now we have full support for the latest versions of Internet Explorer, Firefox, Opera, Safari, and Mozilla. We've found bugs in Konqueror and as of now we have no plans on fully supporting it.
03/28/2006 - We updated the repository with a lot of bug fixes. The bug tickets opened here have all been resolved. Thanks for the feedback. As of now, the Manager Options page has bugs. We will be updating that page with a new version in the next couple of days.
Download the zipped source from [download:peerreviewplugin here].
See user documentation
- 15598 by Cinc-th on 2016-06-15 10:19:33
PeerReviewPlugin: corrected too broad exception clausel.
- 15597 by Cinc-th on 2016-06-15 09:54:13
PeerReviewPlugin: print full path of files in review reports by prepending the repository url.
- 15596 by Cinc-th on 2016-06-15 09:38:20
PeerReviewPlugin: refactored code for building the repository list into a function for future use.
Got some comments about our plugin? Leave them right here.
Comment by anonymous on Sun 23 Apr 2006 08:36:39 EST
Can you put a screenshot? Thanks!
Comment by Team5 on Wed 26 Apr 2006 06:21:52 EST
We sure can - see below. Thanks for the suggestion.
Comment by Tim on Mi 10 mai 2006 21:22:15 EST
We 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 ?