From: David Abrahams (dave_at_[hidden])
Date: 2006-05-12 17:40:22
"Arkadiy Vertleyb" <vertleyb_at_[hidden]> writes:
> "Beman Dawes" <bdawes_at_[hidden]> wrote
>> The problems with the current release approach are not caused by release
>> managers or developers, but rather by the release system itself. It just
>> doesn't scale up to the number of libraries now in Boost, since every
>> library has to be ready before a release can occur.
>> These problems will only grow worse as more libraries are added.
> I think you are considering just one dimension of the problem.
> The other one -- the number of supported compilers is IMO equaly, if not
> even more, important. The broken build can be detected only after the
> regressions run on all the compilers. Which may be a few days (or a few
Making sure that incremental testing works reliably may be the best
way to address that problem.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk