[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Code Reviews

From: MikeW <mw_phil_at_yahoo.co.uk>
Date: 2007-05-24 09:58:35 CEST

 <dcaldwel <at> danielcaldwell.com> writes:
> Does anyone have any good strategies for tracking code reviews with
subversion? I'm thinking of tagging
> after every code review and comparing between tags, but that seems excessive,
any suggestions? Thanks.
> -Daniel
Depends on how exactly you want to use it - after every bug fix changeset ?

One approach would be to use properties, which could then be set with the
identifier of the reviewer & timestamp, by a script of some kind.

You might consider tying your defect reporting mechanism into the system
to ensure that 'fixed' defects were flagged as crosschecked by a reviewer.

I saw one approach in which the reviewer used a web-based tool
which picked up the files concerned and allowed the reviewer
to add a status (OK; needs rework; rework at next rev) and notes to each file.

The 'fix' only got a green light in the tool once all files got
the OK status.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 24 09:59:14 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.