> > Potential patch conflicts are less of a problem from my PoV than > having a ton of Jiras and commits that haven't gotten past the "ready > for review" stage because people are inherently lazy and it's easier > to not do it.
But the likelihood is that instead you'd get a load of JIRAs with patches on that no-one reviews because they are lazy :-) I think that if we as a group are good at enforcing the review phase then we should be able to make this process workable. Producing automated reports for number of unreviewed commits - plus a summary of how many reviews each developer has done in the past month should I think be sufficient to keep the number of unreviewed changes down to a minimum. -- Rob
