Re:Branchless development
by pvg on Sunday July 19, 2015 @05:54AM
(#9910645)
Isn't that a little at odds with the idea that the author is describing some variant of the OpenBSD development process (unless I misread the thing) and beside being a large and ongoing project, they've been reviewing code since before it became fashionable?
[ Parent
| on HN ]
Re:Branchless development
by jacques_chester on Sunday July 19, 2015 @06:46AM
(#9910755)
The original literature on reviews that gets everyone hot and bothered describes something very different from what is done in practice.
Formal meetings with scribes and reviewers and procedures and checklists are not the same as "here, check out this patch and merge it if you like it".
I haven't kept up with research and I don't know if anyone has shown that TDD + pair programming is a reasonable substitute for full-blown code reviews in terms of bug yield.
Now that I think of it, what I saw was an inversion of the classic CVS commit-bit model. CVS-based opensource projects typically have a praetorian guard who review everything before it gets committed.
What I've generally seen is the reverse: soliciting opinions from other teams with little context or familiarity with the original codebase. So they take days or weeks to respond and when they do, it's quite cursory.