+1
On Tue, Mar 19, 2013 at 1:22 AM, Bruno Mahé <[email protected]> wrote: > On 03/17/2013 12:09 PM, Konstantin Boudnik 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? >> Cos >> > > +1
