Roman Yakovenko writes:

Aleksey Gurtovoy wrote:

...

a) incremental cylces, with a full rebuild once a week or something similar (here at Meta, for instance, are currently doing full rebuild on every cycle);

b) distributed testing of libraries, with the following merging of results into a single report.

I agree with Aleksey. I am using boost a lot in my work. So I would like to give something back. I can test CVS version of boost on WinXP + compiler of MS Visual Studio 7.1. And at home on "Fedora Core 2" gcc 3.4.

The question is what should I send back?

Ideally, the test results in XML that would be then merged and processed to generate a boost-wide report. A bigger issue is that the procedure how to set up and maintain regression tests is largely undocumented and under-automated. The regression system we use here at Meta solves the latter part, but it needs to be documented too; I hope to get it posted sometime next week. -- Aleksey Gurtovoy MetaCommunications Engineering