Re: [boost] Breaking existing libraries

suppose we set up a mailing list to which all the test checkins are posted? Then anyone who wants to monitor the evolution of a library's tests can subscribe to that list.

Dave, I don't know how much email you get a day but this doesn't sounds workable. It's bad enough to try to keep up with the users and devel traffic, let alone with extra emails whenever the developer decides to change a test case. This cannot be automated - I would argue that it should be the responsibility of the library maintainer to let the users know of any large impeding changes.