I filed a request to change the notification:
https://issues.apache.org/jira/browse/INFRA-7995
On Fri, Jun 27, 2014 at 9:21 AM, Robert Metzger wrote:
> I meant comments. We extensively use GitHub's feature to review pull
> requests by doing line-wise comments on the changes. And each of these
>
I meant comments. We extensively use GitHub's feature to review pull
requests by doing line-wise comments on the changes. And each of these
comments is causing a mail to the dev@ list. Since the comments are also
replicated to JIRA and the issues@ list, it is sufficient to sent the mails
to issues@
Did you mean "commits" rather than "comments"? I believe the Apache
best practice is to send commits to the dev list because we want
committers to keep an eye on what's getting committed. We don't want to
put those notices on a heavy traffic, low readership list where people
won't tend to see
+1
That would be great
2014-06-26 14:39 GMT+02:00 Robert Metzger :
> Do you all agree with sending the notifications about new GitHub comments
> to issues@flink.i.a.o as well?
> If you agree, I'll ask Infra to do that for us.
>
>
> On Fri, Jun 20, 2014 at 8:04 PM, Henry Saputra
> wrote:
>
> >
Do you all agree with sending the notifications about new GitHub comments
to issues@flink.i.a.o as well?
If you agree, I'll ask Infra to do that for us.
On Fri, Jun 20, 2014 at 8:04 PM, Henry Saputra
wrote:
> HI All,
>
> We now have iss...@flink.incubator.apache.org list that is used to
> recei
HI All,
We now have iss...@flink.incubator.apache.org list that is used to
received updates from Flink JIRA updates.
Currently we also still send create event from JIRA to dev@ list to
make sure developers know about new JIRA created.
Hopefully this will help reduce "noise" we are seeing with he
