|
|
Boost Testing : |
From: Beman Dawes (bdawes_at_[hidden])
Date: 2005-11-21 13:18:05
"Doug Gregor" <dgregor_at_[hidden]> wrote in message
news:8041ab9cf210585a4d008afae349b6e9_at_cs.indiana.edu...
>
> On Nov 18, 2005, at 3:38 PM, Beman Dawes wrote:
>
>> The i18n branch for Boost.Filesystem should be ready to merge into the
>> CVS
>> HEAD sometime next week.
>>
>> While I'll run tests beforehand on several platforms, this is a big
>> change
>> and it won't be at all surprising if it is broken for some of the
>> platforms
>> and/or compilers I won't be able to test on before the merge.
>>
>> The problem that will cause is that since process_jam_log uses
>> Boost.Filesystem, a breaking change will bring down the testing
>> harness. Is
>> there a way to suppress rebuilds of process_jam_log on tester's
>> machines
>> until Boost.Filesystem has stabilized? Or am I worrying needlessly?
>
> If there is any possibility of danger, the timing worries me a little
> bit. Boost 1.33.1 final is supposed to go out on December 5th, which
> means that "final" testing needs to happen the week before. If the
> Filesystem merge does cause testing issues, it would surely make the
> release slip.
OK. Howabout this: I'll schedule the merge for December 6th. Once I get
everything ready, I'll put up an extract on a web server so anyone who wants
to can download it and try it out beforehand. I was planning to do that
anyhow so C++ committee members could try it.
--Beman