> Fundamentally, our philosophy has been to catch errors *before* they get > into the repository. Sure one day of breaking the trunk isn't so bad, but > when it breaks it affects hundreds of developers and it adds up. Everyone > separately either stops and waits, or tracks down which patch it was and > reverts it so they can continue working.
An interesting question that I see as relevant here and for which I have no data is: what percentage of the time does a patch cause an error *only* in libjava? I think you have to weigh the cost of the build of that library against the number of bugs that it finds.
