On 30 Jun 2008, at 13:38, Christian Lohmaier wrote:
[..]
One needs to put the efforts to the very bottom of the queue, not at
the top of it.
beware - a car-related analogy will follow - as such it will always
have weak points, but I'll try to make my point clear:
If your car doesn't stop when you hit the break, what will you do:
* Buy a louder horn, so that you can alarm people to get out of your
way
* Only drive at 10 km/h, so when you hit stuff, you won't break much
* Fix your breaking system
So I think fixing the breaking system is the best solution (work
towards milestones being what the milestone rules suggest: Always
building, always in a state in such no new problems are introduced)
Of course, driving slowly can help to prevent causes of an accident -
but this doesn't work when running downhill (when a release is near,
you cannot work up all the work that should have been done during the
milestone tests)
If there are fixes for a crashing master I would much rather them
being integrated asap, rather than waiting for ages before they are
integrated.
Shaun
