Robert Ramey wrote:
Speaking of early freezing, I think we should be pragmatic. ....
I would like to see all tests run with the boost build and boost test in the release ready branch. This would permit developers of these tools to feel comfortable about commiting changes which might break something without creating a lot of problems for those using these tools. This would permit boost build to progress at its own schedule and pace while maintaining an ever improving product for use by boost and others. This would eliminate the requirement for any kind of "freeze"
Let me try to have all "i" dotted and "t" crossed: 1. Build.Build has extensive testsuite. 2. It would be nice to have it run together with library tests, to improve Boost.Build quality on some platforms where it's not actively tested by users. It will help Boost.Build users, as well folks who are both C++ Boost users and Boost.Build users. 3. Any such improvement won't help C++ Boost itself much. The only thing C++ Boost cares is whether C++ Boost libraries and tests work. If a change breaking that on some platform is checked in, the current test framework will surely detect this. Adding Boost.Build tests to the mix will only mean the breakage will be detected somewhat earlier and be somewhat easier to figure. So, adding Boost.Build tests to the test results is not something C++ Boost users or developers should care very much about. - Volodya