|Version 34 (modified by anonymous, 8 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 here.
See user documentation
-  by rjollos on 2014-02-19 11:50:40
Fixed indentation and trimmed whitespace using reindent.py.
-  by rjollos on 2013-12-23 03:54:10
Add stylesheets using add_stylesheet. Fixes #10729.
This fixes some incorrect hard-coded paths in link elements in the templates.
-  by rjollos on 2013-12-23 03:25:20
Fixed error from r13497.
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 ?
Comment by szm on Ma 30 mai 2006 04:31:24 EST
This plugin would be much more interesting if it could compare svn diffs rather than having the user mark the changes manually, which is error prone, and difficult to compare against the previous version.
Comment by anonymous on Vi 02 iun 2006 18:13:27 EST
It seems that the plugin interferes with the "source:" form of wiki links. These links do only return a div element, like it may be suitable for ajax requests. Is there a workaround?
Comment by anonymous on Vi 02 iun 2006 18:17:26 EST
hm. and "Add comment" implemented as GET request will lead to the above for people like me, who hit reload every once in a while.
Comment by moisei _ at _ gmail.com on Du 02 iul 2006 07:50:19 EST
Codestriker has really good concept on the code-review process. They use a "source code diff" as the item of review rather than "part of code" as it is done in this plugin. Do you have any plans to move in this direction? I wish to have our code review integrated with trac and I even raised some discussion on this topic.
Comment by anonymous on Tue Oct 17 00:52:10 2006
So is this plugin going to be updated to v0.10 and beyond? And will it be updated to work with changesets as opposed or in addition to revisions?
For 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.