|
Boost : |
Subject: Re: [boost] The problems with Boost development
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2010-03-21 04:29:57
On 03/21/2010 08:14 AM, Vladimir Prus wrote:
> Christopher Jefferson wrote:
>>
>> The point where that breaks down is where one library is found to have
>> a fatal flaw shortly after a release,
> > you wait 6 months (or whatever) for another version of boost which
> fixes the bug, but also breaks the API on
> > a half-dozen other libraries you use.
>
> Is this not a maintenance releases problem again? That is, if there's
> mechanism to quickly roll point
> release when such a flaw is discovered, then it's relatively unimportant
> how monolitihic a design
> is.
It is much easier to ship a maintenance release of a single library than
of the whole Boost. Users will be able to compose their local
distributions of maintenance releases of libraries they use and thus
strive for stability.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk