> I've been thinking of using trac tickets as a code review mechanism. > is anyone else out there doing this?
yes, in a limited way, though I plan to do more... > i plan to create a new type of ticket and name it as review. That's what we do. > How do you normally do code reviews with trac? Our reviews are relatively informal face to face affairs, and often include a lot of models that are not rendered by the CodeReviewPlugin (so we bring them up on the projector / people have print outs of areas they want to discuss) I have the MasterTicketsPlugin installed. We set blocking tickets to be actions from the review ticket. The UI is not particularly elegant (yet) as the "note taker" during the review needs to remember the review ticket number to set it in the blocking field of all the actions. Some users really seem to like the dependency graph. In terms of keeping tabs on what needs to be done, and verifying all the actions are complete before the review is closed, it works OK but not amazing yet. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
