I think commits@f.a.o would be the best place. Builds break because of bad commits (most of the times) Moreover an additional list (ex. builds@f.a.o) would be a bit of an overkill.
Thanks, Om On Sat, Jun 29, 2013 at 12:16 AM, Frédéric THOMAS <webdoubl...@hotmail.com>wrote: > commits@ or issues@ I would say what is better but what is sure is it > pollutes the dev list. > > Those 2 lists are followed as well by committers or at least PMCs, > otherwise what do you thing about another list builds@ ? does it worth ? > > -Fred > > -----Message d'origine----- From: Alex Harui > Sent: Friday, June 28, 2013 4:35 PM > To: dev@flex.apache.org > Subject: Re: Mustella VM emails to 'issues'? > > > > > On 6/28/13 12:32 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > > Hi, >> >> I was just wondering: would it be better if I have Jenkins send the >> Mustella run emails to 'issues@'? >> > Wouldn't commits@ be better? > > >> The way it stands now, all three runs (main, AIR and mobile) have >> tests failing (even after -failures). This means that per full run, >> three emails will be sent... twice a day. That will put even Justin's >> JIRA email production to shame ;-) I think it will be cleaner if I >> direct those emails somewhere they don't interfere with the 'regular' >> discussions? >> > > I'll try to spend some time cleaning up the runs next week. > >
