I would probably still subscribe only to issues@. The created/resolved traffic is already high enough for my interests. When I'm more interested, I become a watcher of tickets on an individual level.
That said, I have no objection to the creation of issues-all@ for those who are interested. On Thu, Feb 8, 2018 at 8:02 AM, Philip Zeyliger <phi...@cloudera.com> wrote: > Hey devs! > > Currently the issues@ mailing list (https://lists.apache.org/ > list.html?iss...@impala.apache.org) gets notifications of JIRA issues that > are created and resolved. > > I'm considering asking our PMC to create a new issues-all@ mailing list and > then asking ASF INFRA to update the JIRA notification scheme to send all > notifications. > > Would other people besides me be interested in issues-all@? > > Based on a sketchy analysis of an RSS feed I found, this would roughly be > double the e-mail volume for people who opt in. There were ~315 comments > vs. ~240 created/resolved notifications in the feed. > > https://issues.apache.org/jira/activity?maxResults=1000&; > streams=key+IS+IMPALA&providers=thirdparty+dvcs-streams-provider+issues&os_ > authType=basic&title=undefined > $grep -o 'category term="[^"]*"' z.txt | sort | uniq -c | sort -n > 2 category term="stopped" > 12 category term="reopened" > 14 category term="closed" > 31 category term="started" > 117 category term="created" > 124 category term="resolved" > 315 category term="comment" > > > Thanks!
