Re: [Boost-build] All tools code frozen!

From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2008-07-18 15:11:04

Jurko Gospodnetic' wrote:
>   Hi Rene.
> 
>> Since I don't enjoy reverting changes when I don't have the time (I'm 
>> in the middle of my own product release). And since Boost is nearing 
>> the end of a release cycle. *ALL* tool changes are hereby *FROZEN* 
>> except for emergency fixes. Any changes must be approved by Beman or 
>> myself. And such changes must include making sure Boost testing runs 
>> adequately in *both* a Windows platform and a Unix platform. This 
>> means going to the boost-root/status directory and running the tests 
>> for *at least one* library, but preferably all of them.
> 
>   Is the release still on schedule and expected to go out after 
> 31.07.2008.?

I think we might be delayed 1 week at most. But Beman has a much better 
sense of that.

>   Just wondering whether to start a new branch for tracking Boost Build 
> changes until the release. There seems to be a few people contributing 
> patches lately and I do not think we should risk disgruntling them due 
> to the code freeze causing their patches not to get processed fast enough.

Either setting up a branch for the continued development would be good. 
Or doing a BBv2 release now, and switching the testing and Boost release 
to match the BBv2 release, would also work. Volodya would have to decide 
if doing a BBv2 release now is a good choice or not. But since library 
developers need to use trunk for their individual testing the former is 
a more desirable route.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org (msn) - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail