Boost Testing :
From: Doug Gregor (dgregor_at_[hidden])
Date: 2005-11-21 11:32:23
On Nov 18, 2005, at 3:38 PM, Beman Dawes wrote:
> The i18n branch for Boost.Filesystem should be ready to merge into the
> HEAD sometime next week.
> While I'll run tests beforehand on several platforms, this is a big
> and it won't be at all surprising if it is broken for some of the
> 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
> 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