I will state again (as I've done on prior email threads) that I find no value in spamming the JIRA issues like this, and that I strongly believe that this behavior is in fact detrimental since it obscures the actual comments on the issue itself. The proposed solution of just moving the destination of the JIRA emails to a different list than [email protected] doesn't solve that root problem.
I want to be able to read a JIRA issue without having to skim over dozens and dozens of auto-appended code review messages. I truly cannot understand why this isn't an annoyance for others. I could be really snarky and reformat this email to have a bunch of random stuff in between every sentence to make my point, but I hope this sentence suffices to prove it? Though I must acknowledge your point Jungtaek that there is some Apache policy that all code review comments need to be archived into some apache system. Maybe we can use the attachment functionality of JIRA instead of making these separate comments on the JIRA issue? I'm not sure how the integration is set up right now, that seems feasible. - Erik On Thu, Aug 11, 2016 at 2:08 AM, Matthias J. Sax <[email protected]> wrote: > I like the idea of have one more mailing list to reduce load on dev-list. > > -Matthias > > On 08/11/2016 11:07 AM, Jungtaek Lim wrote: > > I remember that Taylor stated that all github comments should be copied > to > > somewhere Apache infra, and it's Apache JIRA for us. > > > > It seems to make sense but I'm curious other projects respect this rule. > I > > also subscribed dev list of Kafka, Zeppelin, Flink, HBase, Spark > (although > > I barely see them) but no project is sending mail per each comment. Some > of > > them copy github comments to JIRA issue but no notification, and others > > doesn't even copy comments to JIRA issue. > > (You can check this with dev mailing list archive, too.) > > > > I'm in favor of reducing simple notification mails. Personally I saw most > > of Storm dev. mails so I'm fine to keep mailing as it is (with some > > annoying 'empty' notification), but it can also be done with watching > > Github project. > > > > This is not raised for the first time, and I would like to discuss > > seriously and see the changes. > > > > Thanks, > > Jungtaek Lim (HeartSaVioR) > > > > 2016년 8월 11일 (목) 오후 2:22, Kyle Nusbaum <[email protected] > d>님이 > > 작성: > > > >> There seems to be a surplus of automatically-generated emails on the dev > >> mailing list. > >> Github and Apache's Jira constantly send mails to the dev list. > >> > >> I'm not sure that anyone finds these useful. Even if they do, I wonder > if > >> its better to move them to a separate list. It's possible that everyone > has > >> email filters employed to sort this out, but if every subscriber has the > >> same filters employed, it might indicate the need for a separate list. > -- > >> Kyle > > > >
