(this was prompted by me interrupting a quasi-appropriate JIRA meta-discussion about JIRA workflow & permissions (on an issue I had opened because I encountered it whilst working another issue, and had fixed but not PRed, which Stefan then also fixed) to further apologize to Stefan for not replying to an email from him (on dev) that I'd missed because of coveralls) .
So +1. Also, I need to reply to that email :) Simon On Jun 19, 2017 6:33 AM, "Stefan Bodewig" <bode...@apache.org> wrote: Hi all apart from dev@ and user@ we've got three lists that have been created for specific notifications that people may be interested in or not: issues, commits and notifications. My MUA is configured to merge those three with dev so I didn't really notice we are getting more messages (and for most people more noise) to dev than I would have expected. JIRA seems to be set up to send to issues@ for all components, and the git and svn commit messages of components go to commits@ while svn commit messages for the website go to notifications@. Things are different between components for at least * github integration (some components like Compress send mails to dev, others like Numbers send them to notifications) * CI messages (at least Compress uses dev for Jenkins mails) IMHO neither should go to dev@ and using notifications@ seems more logical to me. I'm going to change this for Compress and would likt to ask other components to check their settings as well so we can raise the signal ratio for dev@ again. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
