Introducing [e-mail] mailing list

[Henry Saputra]

HI All,

We now have [hidden email] 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:
    [hidden email]


Thanks,

- Henry

[Robert Metzger]

Do you all agree with sending the notifications about new GitHub comments
to [hidden email] 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 <[hidden email]>
wrote:

> HI All,
>
> We now have [hidden email] 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:
>     [hidden email]
>
>
> Thanks,
>
> - Henry
>

[Fabian Hueske-2]

+1

That would be great


2014-06-26 14:39 GMT+02:00 Robert Metzger <[hidden email]>:

> Do you all agree with sending the notifications about new GitHub comments
> to [hidden email] 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 <[hidden email]>
> wrote:
>
> > HI All,
> >
> > We now have [hidden email] 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:
> >     [hidden email]
> >
> >
> > Thanks,
> >
> > - Henry
> >
>

[Alan Gates]

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.

[hidden email]

June 26, 2014 at 5:39 AM

Do you all agree with sending the notifications about new GitHub comments
to [hidden email] 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 [hidden email]

[hidden email]

June 20, 2014 at 11:04 AM

HI All,

We now have [hidden email] 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:
[hidden email]


Thanks,

- Henry

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.

[Robert Metzger]

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 <[hidden email]> 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 <[hidden email]>
>  June 26, 2014 at 5:39 AM
> Do you all agree with sending the notifications about new GitHub comments
> to [hidden email] 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 <[hidden email]>
> <[hidden email]>
>
>   Henry Saputra <[hidden email]>
>  June 20, 2014 at 11:04 AM
> HI All,
>
> We now have [hidden email] 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:
> [hidden email]
>
>
> 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.

[Robert Metzger]

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 <[hidden email]> 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
> 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 <[hidden email]> 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 <[hidden email]>
>>  June 26, 2014 at 5:39 AM
>> Do you all agree with sending the notifications about new GitHub comments
>> to [hidden email] 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 <[hidden email]>
>> <[hidden email]>
>>
>>   Henry Saputra <[hidden email]>
>>  June 20, 2014 at 11:04 AM
>> HI All,
>>
>> We now have [hidden email] 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:
>> [hidden email]
>>
>>
>> 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.
>
>
>