Boost logo

Boost :

Subject: Re: [boost] 1.37 release schedule?
From: Eric Niebler (eric_at_[hidden])
Date: 2008-10-09 12:18:50

Vladimir Prus wrote:
> Beman Dawes wrote:
>> On Thu, Oct 9, 2008 at 12:43 AM, Eric Niebler <eric_at_[hidden]>wrote:
>>> Rene Rivera wrote:
>>>> Something in the doc build also prevented me from doing a bjam release two
>>>> weeks ago :-( So I'll have to try and get a bjam release done ASAP, and
>>>> merged into the release. But ASAP for me right now means the weekend. So is
>>>> it OK to do this merge?
>>> I'm not wild about this, actually. It makes me more than a little
>>> uncomfortable to think about upgrading the build system this late in the
>>> release cycle.
>> I share Eric's concern.
>>> Changes to critical infrastructure (like build and test) are best done at
>>> the start of the cycle.
>> Exactly.
> Aren't trunk tests supposed to show if build and/or test are working fine?

Testing first on trunk is an important safe-guard against instability on
the release branch. But even with that safe-guard in place, instability
on release *will* happen at some point -- no system is perfect. And
stable build and test tools are so important to our ability to deliver
releases on time that holding them to a higher standard is perfectly
reasonable, IMO.

Let's let Rene explain the nature of the changes and assess the risk.

Eric Niebler
BoostPro Computing

Boost list run by bdawes at, gregod at, cpdaniel at, john at