I agree that openafs-devel is a good place to start. If it becomes a nuisance with too much traffic, people should please speak up and we can come up with an alternative.
-Ben On Mon, 26 Jan 2015, Dave B. wrote: > State change to openafs-devel or some alias of the admins of the slaves is a > good start. > > ******************************** > David William Botsch > Programmer/Analyst > @CNFComputing > [email protected] > ******************************** > > > > On January 25, 2015 7:47:03 PM Jason Edgecombe <[email protected]> > wrote: > > > On 01/25/2015 06:16 PM, Jeffrey Altman wrote: > > > On 1/25/2015 5:52 PM, Jason Edgecombe wrote: > > >> Where should these status emails be sent? Perhaps to > > >> [email protected]? > > > [email protected] receives the announcements of merges to the > > > repository. > > > > > > I would be in favor of having the nightly builder failures sent to > > > [email protected] or [email protected]. I'm leaning > > > towards openafs-bugs because that opens an RT ticket for the failure. > > > On the other hand, very few people monitor RT and developers are more > > > likely to see a failure on the openafs-devel list. > > > > > I like idea of emailing openafs-devel. If multiple builders fail, then > > the email traffic might be a bit much given the the twice daily builds > > of the master and 1.6 branches. We could use the state change emails in > > that case, but things might not get fixed if the initial breakage email > > was lost. > > > > Jason > > _______________________________________________ > > OpenAFS-devel mailing list > > [email protected] > > https://lists.openafs.org/mailman/listinfo/openafs-devel > > > _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
