On Tue, Jul 04, 2006 at 10:45:11AM +0200, Asger Ottar Alstrup wrote: > The main risks are: > > - There will be a known problem which the developer does not have time > to fix until a week or two later. Then something happens, and it never > gets done
This is still a risk even with review. Review won't catch all bugs. I don't see this as a serious issue. > - A developer does dangerous changes because of lack of experience or > skill (no developer knows all platforms or all history) > > - Others will have to spend a lot of time to clean up abandoned stuff, > because the original coder does not have time to fix it - no review is ever done at all > 3) Commit early and often. When doing a sprint, commit each logical, > working change rather than one big commit at the end. But as I understand it, this is the bone of contention anyway. If they need to do this, it is not a huge burden to get patch review, surely. regards john
