I don't think we should send ci to a different email list for it to be ignored. We ideally should be in a place where emails from ci are not the norm but an exception which prompts immediate action.
On Tue, Mar 20, 2018 at 3:05 PM Dan Smith <dsm...@pivotal.io> wrote: > +1 to removing all automated messages from dev@geode > > I think we've already shunted commit messages to commits@geode and jira > issue updates to issues@geode. What I see now is mostly messages related > to > ci. Should we create a new ci@geode mailing list, or send those messages > to > some other mailing list? > > If we want to create a new list, I think the next step is to file a ticket > with infra after we come to a consensus. Unless our illustrious leader Mark > has access to do that :) > > To move the CI emails to the the new list, we'll have to update concourse, > jenkins, travis, and spring CI it looks like. > > -Dan > > On Tue, Mar 20, 2018 at 2:27 PM, Galen O'Sullivan <gosulli...@pivotal.io> > wrote: > > > Hi all, > > > > I'm wondering if it would be possible to have a separate list for commit > > announcements, CI emails and similar automated messages, and keep this > > mailing list for discussion. It would make it easier to filter email, > and I > > think it might help improve the discussion. I know I've missed messages > > sent to this list in the flood of email. What do you think? Who's in > charge > > of lists and gets to make those decisions? > > > > Thanks, > > Galen > > >
