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.
