Guys, as soon as INFRA-9358 <https://issues.apache.org/jira/browse/INFRA-9358> is resolved dev@ list looks much better now but is still kind-of flooded with GH PR comments notifications.
What if we exclude GH PR comments from the dev@ list too? We can keep comments notification to GH users who are subscribed to PR or watching the issue in JIRA (because of GH<->JIRA integration). We also can keep "PR created" notification on the list for now (but I'm not sure if that is still a good practice or not because they are reflected in JIRA already) If there are no objections I will proceed and file another INFRA issue (as a followup of INFRA-9335 <https://issues.apache.org/jira/browse/INFRA-9335>) to do that. Thanks! On Wed, Apr 1, 2015 at 3:39 PM, Alex B. <[email protected]> wrote: > There was already a discussion here to mute JIRA notifications (keep only > 'issue creation' forward to dev@) which resulted in > https://issues.apache.org/jira/browse/INFRA-9358 > > The problem right now is that EVERY comment on PR comes twice to dev@: > once from GH and once from JIRA (because GH-JIRA integration we have) > I suggest we keep GH-JIRA integration but turn off "comment creation > notification to dev@" for both, JIRA (in progress) and GH mirror. > > Having separate lists sounds not bad to me, but we already have two, so > there is a risk that a the end less attention will be payed to each of them > on average.. > > > On Wed, Apr 1, 2015 at 1:30 PM, Konstantin Boudnik <[email protected]> wrote: > >> IIRC there were an attempt to move all JIRA notifications to issues@ >> list, is >> it not? >> >> Cos >> >> On Wed, Apr 01, 2015 at 11:43AM, Corneau Damien wrote: >> > I too prefer using basic Github notifications than ASF Git bot, they are >> > more readable. >> > >> > We can't really turn everything off because it's part of Apache Zeppelin >> > discussions, but filtering so that people can subscribe if they want is >> > better. >> > For the duplicates however, it would be nice to turn it off. >> > >> > On Wed, Apr 1, 2015 at 11:32 AM, Kevin Kim (Sangwoo) <[email protected]> >> > wrote: >> > >> > > My eye was bleeding for too many emails, too. >> > > I filtered out all emails from ASF Git bot and just using dev@ >> mailing >> > > list >> > > and email from github. >> > > >> > > On Wed, Apr 1, 2015 at 11:29 AM Corneau Damien <[email protected] >> > >> > > wrote: >> > > >> > > > Hi, >> > > > >> > > > I find it difficult to follow the dev mailing list recently, there >> is a >> > > lot >> > > > of noise because of JIRA and GITHUB. We even get some emails twice >> > > (GITHUB >> > > > comment on JIRA issues). >> > > > >> > > > Some projects have different mailing list to separate all of those. >> > > > >> > > > For example: >> > > > >> > > > 'issues' for JIRA >> > > > 'reviews' for Pull Request >> > > > >> > > > And I think it could be a good idea to do the same. >> > > > >> > > > Anybody has some suggestions? >> > > > >> > > >> > > > > -- > -- > Kind regards, > Alexander. > > -- -- Kind regards, Alexander.
