Looks like everybody is in favor. I am going to file INFRA ticket and once the maillist is created, we'll deal with the builds' and JIRA's notifications.
Cos On Mon, Mar 18, 2013 at 09:18AM, Roman Shaposhnik wrote: > On Sun, Mar 17, 2013 at 12:09 PM, Konstantin Boudnik <[email protected]> wrote: > > I have been searching for an old email in our mailing list and I have > > just realized that the archives are literally polluted with something > > like " Build failed in Jenkins" or " [jira] [Commented] " > > > > In every given month there are screens and screens of the emails that > > either dups of the information available elsewhere - i.e. Jira, or > > useless in the retrospect - Jenkins build failure notifications are of > > no importance in a couple of days usually. > > > > What do you guys think about redirecting all that traffic to a > > separate list and leave the dev@ for human beings? Say, we might have > > another list ci@ or similar where all jira comments and jenkins > > notifications will be sent. > > > > I don't buy the argument like "this will hide important notifications > > from the developers" simply because most of us are filtering these > > notifications one way or another in order to make inbox inflow > > manageable. For instance, I have a filter that moves all JIRA and CI > > notifications for different projects to their appropriate mailboxes > > that are being checked upon when I have time for it, etc. > > > > So, what do you think? > > +1. I think we've grown quite a bit for this to make sense. > > Thanks, > Roman.
