Re: automated build/testing?

On Tue, 2005-06-14 at 15:53, Robert Story wrote:
> As long as we seed the subscription with the admin list, that's ok.

Yes, that would be sensible.

> My concern with a separate list is that the admins won't subscribe.

I think my main concern is to have the flexibility to choose how
closely involved I am involved at any particular time. When I
took that step back from the project just after Christmas, it
brought home to me just how much time was being taken up with
following Net-SNMP email (let alone responding to it!)

Unsubscribing from the bugs, patches and CVS lists has felt
like a significant lessening of the workload - probably way out
of line with the actual amount of traffic involved.

The advantage of a separate testing list is that it would
allow me to take a step back as/when necessary (like probably
at the start of the academic year), without feeling the need
to unsubscribe from the coders list completely.


> Maybe a time threshold (say 3 days) for adding a CC to the
> admin list if the build hasn't been fixed?

I'm not sure we need to formalise things to that sort of level
just yet. Start by seeding the testing list with all the admins,
so we can remove ourselves if we need to, and see how well it
works. If we discover that problems are just getting ignored,
then we can look at how to address that. But let's start simple.

Dave



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders