Many developers out there these days either are forced to, or voluntarily, do peer code reviews. The biggest problems that the peer code review process faces, IMO, are:
A) One shouldn't check changes into one's VCS system until you've had your code review. The easiest way to do this is to grab someone and have them review your changes right before you check them in. But what if that person is busy? What if you need to get onto other things? What if that person is somewhere else in the world?
B) No easy way to keep documentation on what was code reviewed, what the reviewer's comments/suggestions were, or what the reviewee did about it. This information can be useful to both developers and management in various ways.
C) Configurable workflow definition for review process. If manual, "grab a peer" reviews are done, everyone does a review in their own way. As a project grows, the list of things to make sure new/revised code does increases, and it's sometimes hard to make sure you cover everything in a code review.
There look to be a couple of things out there that try to address this problem:
Cenqua Crucible: http://www.cenqua.com - won't be out until next year. No demo or beta available as of yet.
Jupiter Eclipse Plugin: http://csdl.ics.hawaii.edu/Tools/Jupiter/ - haven't tried it as I don't use Eclipse.
Are there any other tools out there that I don't know about?
The whole point of this thread is that I would love to see something like this integrated into Idea. It seems that XP (eXtreme Programming) is taking hold at more and more places, and peer code reviews are more and more becoming a requirement of our daily lives as software developers. This could be a killer feature for Idea that would differentiate it from it's competitors even further.
I'd love to hear what other people think about this issue.