Robert Ramey wrote:
I'm interested in the process whereby these changes occur.
I would like to see
a) trunk testing continue with the "last release" of bjam. b) the trunk testing to include testing of at least one boost tool - bjam. c) when trunk testing passes, then boost build changes can be merged into the release - just as a normal library. At this point, the Boost Build from the release ready branch would be used by trunk testing.
It's my understanding that boost.build has its own test suite so implementing trunk testing should entail little or no extra work. Though I would expect that as in testing of libraries, new problems motivate the addition of new tests. This is a good thing.
I believe that this would make implementing big changes in boost build easier for everyone.
I'll see if I'll be work on including Boost.Build tests in the matrix fast enough to make it for 1.38. (As practice shows, if any failures turn up they are hard to fix without actual access to the system running tests, so I not sure how much gain it will be) - Volodya