The part that breaks occam's razor principle is: The community responds quickly with a fixing patch.
On Fri, Dec 19, 2014 at 4:45 PM, stewart mackenzie <[email protected]> wrote: > > The minimal idea is: maintainers dont do 'deep' code reviews. They > just glance over the patch and make sure it qualifies as a correct > patch, as defined by C4. After travis goes green they hit merge. > > If a bug gets in, its not their fault. The community responds quickly > with a fixing patch. > > Main points a maintainer is aware of: no public API breakages and it > compiles. (travis does wonders for point 2). > > This rather counter intuitive approach means contributors become more > careful. It also means more eyeballs are watching and when shit hits > the fan its all hands on deck. > _______________________________________________ > nix-dev mailing list > [email protected] > http://lists.science.uu.nl/mailman/listinfo/nix-dev >
_______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
