From: Thomas Witt (witt_at_[hidden])
Date: 2007-06-06 19:28:35
Gennadiy Rozental wrote:
> It can be and it should be. Release can't wait for me to commit/merge even
> single byte.
This is true in so many ways :(
>> The problem with testing is not monitoring test results. The problem is
>> managing the
>> testing itself. I.e. making sure tests run as needed, making sure only the
>> "right" people
>> submit release tests, debugging bogus results, monitoring the reporting,
>> in case of a
>> genuine regression tracking it to a specific change. These things need to
>> be taken off the
>> table. Most of this can be achieved by fixing the regression test system.
> IMO this is orthogonal to the boost release procedures (or it should be)
No it's not. It's at the core. No procedure in the world will help you when you have no
way of telling what the status of your project is. It's like having the best possible map
with no way to tell where you are. It's useless.
-- Thomas Witt witt_at_[hidden]
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk