we use a combination of peer review (no code gets commited without a revisor: <user> ) and tag each commit with its associated JIRA issue (just puttin the issue name in the commit comment). That way, with the JIRA plugin, we can see for each funcionality associated commits, etc etc
on a (unrelated) note, ive tried mylar, but it was slightly slugish for me to enjoy (and also, it works best if everyone is using it too and attaching each "viewset" in each JIRA issue) On Sat, Jan 30, 2010 at 1:43 PM, Rakesh <rakesh.mailgro...@gmail.com> wrote: > Hi all, > > I've been tasked with monitoring all the dev check ins so I can do a code > review. We've had alot of issues around code quality. > > Essentially, I need to be able to know what java classes were involved in a > piece of functionality and then go through it with the dev. > > Is there a way to do this? I guess either need to track changes by a > particular dev (over a certain time period) or ask the devs to put some > marker in the check in comment (probably the story number)? > > We use subversion. So I guess some magic command line tinkering? What about > the code review tools out there? > > Cheers > > Rakesh -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to javapo...@googlegroups.com. > To unsubscribe from this group, send email to > javaposse+unsubscr...@googlegroups.com<javaposse%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- http://mapsdev.blogspot.com/ Marcelo Takeshi Fukushima -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
