|
Boost : |
Subject: Re: [boost] Breaking existing libraries
From: David Abrahams (dave_at_[hidden])
Date: 2008-11-30 19:37:27
on Mon Nov 24 2008, "Tomas Puverle" <Tomas.Puverle-AT-morganstanley.com> wrote:
>> 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.
Along with filtering rules, it can be managed.
> 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.
Of course it is, but the suggestions to which I responded seemed not to
be aimed at leaving it _entirely_ in the hands of the maintainers.
-- Dave Abrahams BoostPro Computing http://www.boostpro.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk