JCR also know as jcodereview is a web application for performing and managing code reviews.
Although it has some special smarts for reviewing Java projects, it can be used for reviews of any type of source code.
At work (Dialect Solutions), we use JCR to review more than half of the code we write. It's made a huge difference to our review process - code reviews now take less time, and the code gets reviewed much more thoroughly than it did in the past.
JCR is released under the GNU Public Licence.
Here are some key features of "JCR":
· Reviewers. All changes to code are highlighted, and context is shown when adding comments. If reviewing Java code, references to other classes within the file are clickable, so that you can drill into the detail if required. After review comments have been made, those comments can themselves be reviewed, and the required actions decided on and tracked
· Project owners. Review projects are easy to create and configure
· Process Nazis. Details of all comments are held in the database, along with any actions required, and whether they've been completed. Status reports can be viewed at any time
· Architects and developers. As well as viewing the comments made for a project, it's possible to see details of all review projects and comments for a specified file.
· A suitable Python database driver - PyGreSQL (for Postgres) or MySQLdb (for MySQL)
What's New in This Release: [ read full changelog ]
· Added number of comments for each project on the main page. Note that these only refresh every minute, so they may not be up to date.
· Added explicit wordbreaks between path and filename, to help IE realise it can wrap the text. This should prevent the page being wider than the browser window in IE. Still no good solution for Safari...
· Added 'suggest' functionality to repository path field when creating new project (Subversion)
· Added information icon to Files tab page if no files already selected
· Removed option to select HEAD as original revision (Subversion)
· When HEAD is selected as modified revision, this is replaced (on submit) by the latest revision number in the repository (Subversion)
· Added hints for revision values on File Sets page (Subversion)
· If diff generation fails for any reason, the project should now be returned to the 'Initial Setup' state. You'll still need to check the log to find out why the diff failed
· BUG: Validation of revision did not ensure that revision was valid for the project path (Subversion)
· Added summary statistics for projects as on main page
· Removed logging to console when generating default config file.