I have no issues with issue messages sent to the dev list. I just turned it off for them and routed them to a folder. Were these to contain sizeable attachments that my mail client insisted on downloading, that could be a problem, at least for some.
louis On 18 January 2015 at 12:42, Dave Fisher <[email protected]> wrote: > Olingo does most all of their dev emails through JIRA issues. > > It works for them. Same with legal-discuss. > > I am for putting them on the dev list. If we do bulk changes then the > flood can be handled by turning off the notifications. > > If the project want these on another mailing list that's ok - I will route > to the same folder in my mail client. > > Regards, > Dave > > On Jan 18, 2015, at 8:44 AM, Dennis E. Hamilton wrote: > > > I would prefer that all the noise that JIRA makes for the simplest > changes go to a separate list. > > > > I can handle that locally, and I see I need to fix my email filters and > put things in a Corinthia/Issues folder better. > > > > What I end up having to do is currently, curate what I see in the dev @ > corinthia with what comes to my mailbox because I am following an issue. > Part of the problem is how some email from ASF systems does not identify > the source, but the person who performs an action, so it is necessary to > mine the email headers to figure out what the actual source is and where > things can go. Then spam filters mess it all up anyhow. > > > > I don't think having JIRA notices of the kind we have been seeing go to > the commits list is helpful. Commits are very different. It would be cool > if an issue-related commit could cause a JIRA comment tied to the commit, > but I wouldn't put them all in the same reporting stream. > > > > - Dennis > > > > -----Original Message----- > > From: Andrea Pescetti [mailto:[email protected]] > > Sent: Sunday, January 18, 2015 06:14 > > To: [email protected] > > Subject: Re: Jira and tons of mails. > > > > jan i wrote: > >> Ps. I was wondering, should we move jira mail to commits@ to have less > >> noise in here ? > > > > Possibly, but it's complex. I mean, the fact that issue metadata change > > is not relevant to this list, but maybe sending to the dev list > > (additionally) a notification when a JIRA issue is opened (so when you > > open an issue both lists are notified, then everything else is on the > > commits list only) would help. This way the dev list is always > > up-to-date with respect to development. But I realize this is complex > > and I'm fine with moving JIRA notification to the commits list or keep > > them here. > > > > Regards, > > Andrea. > > > > -- Louis Suárez-Potts Mobile: +1.416.625.3843 (ET) Skype: louisiam Twitter: @luispo G+: https://plus.google.com/+LouisSuárezPotts <https://plus.google.com/+LouisSu%C3%A1rezPotts>
