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@ as well.
On Thu, Jun 26, 2014 at 4:15 PM, Alan Gates <[email protected]> wrote: > 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 them. > > If you really meant comments rather than commits, ignore the above. > > Alan. > > Robert Metzger <[email protected]> > June 26, 2014 at 5:39 AM > Do you all agree with sending the notifications about new GitHub comments > to [email protected] 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 <[email protected]> > <[email protected]> > > Henry Saputra <[email protected]> > June 20, 2014 at 11:04 AM > HI All, > > We now have [email protected] 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 heavy > traffic of JIRA communications in the dev@ list. > > If you interested to listen to Flink JIRA updates please subscribe by > sending email to: > [email protected] > > > Thanks, > > - Henry > > > -- > Sent with Postbox <http://www.getpostbox.com> > > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity > to which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You.
