You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Kenneth Knowles <ke...@apache.org> on 2018/10/15 16:55:54 UTC

[DISCUSS] Separate Jenkins notifications to a new mailing list

Separating this out from the Jira notification thread.

Colm suggests that we also separate build notifications.

WDYT?

Kenn

Re: [DISCUSS] Separate Jenkins notifications to a new mailing list

Posted by Maximilian Michels <mx...@apache.org>.
+1 I can switch of all my filters then, and people new here will be less 
overwhelmed by email.

On 16.10.18 12:46, Alexey Romanenko wrote:
> +1
> 
>> On 16 Oct 2018, at 00:02, Chamikara Jayalath <chamikara@google.com 
>> <ma...@google.com>> wrote:
>>
>> +1 for new lists.
>>
>> Thanks,
>> Cham
>>
>> On Mon, Oct 15, 2018 at 12:09 PM Ismaël Mejía <iemejia@gmail.com 
>> <ma...@gmail.com>> wrote:
>>
>>     +1
>>     On Mon, Oct 15, 2018 at 8:14 PM Mikhail Gryzykhin
>>     <migryz@google.com <ma...@google.com>> wrote:
>>     >
>>     > +1 also suggested that in another thread.
>>     >
>>     > --Mikhail
>>     >
>>     > Have feedback?
>>     >
>>     >
>>     > On Mon, Oct 15, 2018 at 11:10 AM Rui Wang <ruwang@google.com
>>     <ma...@google.com>> wrote:
>>     >>
>>     >> +1
>>     >>
>>     >> Agree that people might be only interested in JIRA activities
>>     but not in the build.
>>     >>
>>     >>
>>     >> -Rui
>>     >>
>>     >> On Mon, Oct 15, 2018 at 10:27 AM Andrew Pilloud
>>     <apilloud@google.com <ma...@google.com>> wrote:
>>     >>>
>>     >>> +1. A bunch of Jenkins spam goes to dev as well. Would be good
>>     to it all to a new list.
>>     >>>
>>     >>> Andrew
>>     >>>
>>     >>> On Mon, Oct 15, 2018 at 10:00 AM Colm O hEigeartaigh
>>     <coheigea@apache.org <ma...@apache.org>> wrote:
>>     >>>>
>>     >>>> As a rationale, some users might be interested in seeing JIRA
>>     activity but might not care about whether the build is broken or
>>     not :-)
>>     >>>>
>>     >>>> Colm.
>>     >>>>
>>     >>>> On Mon, Oct 15, 2018 at 5:56 PM Kenneth Knowles
>>     <kenn@apache.org <ma...@apache.org>> wrote:
>>     >>>>>
>>     >>>>> Separating this out from the Jira notification thread.
>>     >>>>>
>>     >>>>> Colm suggests that we also separate build notifications.
>>     >>>>>
>>     >>>>> WDYT?
>>     >>>>>
>>     >>>>> Kenn
>>     >>>>
>>     >>>>
>>     >>>>
>>     >>>> --
>>     >>>> Colm O hEigeartaigh
>>     >>>>
>>     >>>> Talend Community Coder
>>     >>>> http://coders.talend.com <http://coders.talend.com/>
>>
> 

Re: [DISCUSS] Separate Jenkins notifications to a new mailing list

Posted by Rui Wang <ru...@google.com>.
Thanks Kenneth for handling this!

-Rui

On Thu, Oct 25, 2018 at 8:47 AM Kenneth Knowles <ke...@apache.org> wrote:

> OK, this is done. All emails go to builds@.
>
> Kenn
>
> On Mon, Oct 22, 2018 at 7:12 AM Kenneth Knowles <ke...@apache.org> wrote:
>
>> OK, builds@beam.apache.org now exists.
>>
>> I've opened https://github.com/apache/beam/pull/6775 to migrate but
>> first make the discussion more specific. There are three types of
>> notifications that are treated differently:
>>
>>  - postcommits, etc, which were going to commits@
>>  - nightly release failures which were going to dev@
>>  - seed job failures which were going to dev@
>>
>> They were different because they are different severity and frequency. I
>> don't use email for tracking their status anyhow, but would also happily
>> leave the dev@ jobs as-is if anyone does find it useful.
>>
>> Kenn
>>
>> On Tue, Oct 16, 2018 at 8:14 AM Kenneth Knowles <ke...@apache.org> wrote:
>>
>>> Hi all,
>>>
>>> I moved pretty quickly and without adequate announcement of the
>>> establishment issues@ alias. Sorry if that caught anyone by surprise.
>>> This time I want to properly announce, but the support is pretty
>>> overwhelming so I'll just get the list set up as there's some latency on
>>> that. I'll let 72 hours pass before asking infra to flip the bit.
>>>
>>> Kenn
>>>
>>> On Tue, Oct 16, 2018 at 4:43 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
>>> wrote:
>>>
>>>> +1
>>>>
>>>> Regards
>>>> JB
>>>> Le 16 oct. 2018, à 12:46, Alexey Romanenko <ar...@gmail.com>
>>>> a écrit:
>>>>>
>>>>> +1
>>>>>
>>>>> On 16 Oct 2018, at 00:02, Chamikara Jayalath <ch...@google.com>
>>>>> wrote:
>>>>>
>>>>> +1 for new lists.
>>>>>
>>>>> Thanks,
>>>>> Cham
>>>>>
>>>>> On Mon, Oct 15, 2018 at 12:09 PM Ismaël Mejía <ie...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> +1
>>>>>> On Mon, Oct 15, 2018 at 8:14 PM Mikhail Gryzykhin <mi...@google.com>
>>>>>> wrote:
>>>>>> >
>>>>>> > +1 also suggested that in another thread.
>>>>>> >
>>>>>> > --Mikhail
>>>>>> >
>>>>>> > Have feedback?
>>>>>> >
>>>>>> >
>>>>>> > On Mon, Oct 15, 2018 at 11:10 AM Rui Wang <ru...@google.com>
>>>>>> wrote:
>>>>>> >>
>>>>>> >> +1
>>>>>> >>
>>>>>> >> Agree that people might be only interested in JIRA activities but
>>>>>> not in the build.
>>>>>> >>
>>>>>> >>
>>>>>> >> -Rui
>>>>>> >>
>>>>>> >> On Mon, Oct 15, 2018 at 10:27 AM Andrew Pilloud <
>>>>>> apilloud@google.com> wrote:
>>>>>> >>>
>>>>>> >>> +1. A bunch of Jenkins spam goes to dev as well. Would be good to
>>>>>> it all to a new list.
>>>>>> >>>
>>>>>> >>> Andrew
>>>>>> >>>
>>>>>> >>> On Mon, Oct 15, 2018 at 10:00 AM Colm O hEigeartaigh <
>>>>>> coheigea@apache.org> wrote:
>>>>>> >>>>
>>>>>> >>>> As a rationale, some users might be interested in seeing JIRA
>>>>>> activity but might not care about whether the build is broken or not :-)
>>>>>> >>>>
>>>>>> >>>> Colm.
>>>>>> >>>>
>>>>>> >>>> On Mon, Oct 15, 2018 at 5:56 PM Kenneth Knowles <ke...@apache.org>
>>>>>> wrote:
>>>>>> >>>>>
>>>>>> >>>>> Separating this out from the Jira notification thread.
>>>>>> >>>>>
>>>>>> >>>>> Colm suggests that we also separate build notifications.
>>>>>> >>>>>
>>>>>> >>>>> WDYT?
>>>>>> >>>>>
>>>>>> >>>>> Kenn
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>>> --
>>>>>> >>>> Colm O hEigeartaigh
>>>>>> >>>>
>>>>>> >>>> Talend Community Coder
>>>>>> >>>> http://coders.talend.com
>>>>>>
>>>>>
>>>>>

Re: [DISCUSS] Separate Jenkins notifications to a new mailing list

Posted by Kenneth Knowles <ke...@apache.org>.
OK, this is done. All emails go to builds@.

Kenn

On Mon, Oct 22, 2018 at 7:12 AM Kenneth Knowles <ke...@apache.org> wrote:

> OK, builds@beam.apache.org now exists.
>
> I've opened https://github.com/apache/beam/pull/6775 to migrate but first
> make the discussion more specific. There are three types of notifications
> that are treated differently:
>
>  - postcommits, etc, which were going to commits@
>  - nightly release failures which were going to dev@
>  - seed job failures which were going to dev@
>
> They were different because they are different severity and frequency. I
> don't use email for tracking their status anyhow, but would also happily
> leave the dev@ jobs as-is if anyone does find it useful.
>
> Kenn
>
> On Tue, Oct 16, 2018 at 8:14 AM Kenneth Knowles <ke...@apache.org> wrote:
>
>> Hi all,
>>
>> I moved pretty quickly and without adequate announcement of the
>> establishment issues@ alias. Sorry if that caught anyone by surprise.
>> This time I want to properly announce, but the support is pretty
>> overwhelming so I'll just get the list set up as there's some latency on
>> that. I'll let 72 hours pass before asking infra to flip the bit.
>>
>> Kenn
>>
>> On Tue, Oct 16, 2018 at 4:43 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>
>>> +1
>>>
>>> Regards
>>> JB
>>> Le 16 oct. 2018, à 12:46, Alexey Romanenko <ar...@gmail.com> a
>>> écrit:
>>>>
>>>> +1
>>>>
>>>> On 16 Oct 2018, at 00:02, Chamikara Jayalath <ch...@google.com>
>>>> wrote:
>>>>
>>>> +1 for new lists.
>>>>
>>>> Thanks,
>>>> Cham
>>>>
>>>> On Mon, Oct 15, 2018 at 12:09 PM Ismaël Mejía <ie...@gmail.com>
>>>> wrote:
>>>>
>>>>> +1
>>>>> On Mon, Oct 15, 2018 at 8:14 PM Mikhail Gryzykhin <mi...@google.com>
>>>>> wrote:
>>>>> >
>>>>> > +1 also suggested that in another thread.
>>>>> >
>>>>> > --Mikhail
>>>>> >
>>>>> > Have feedback?
>>>>> >
>>>>> >
>>>>> > On Mon, Oct 15, 2018 at 11:10 AM Rui Wang <ru...@google.com> wrote:
>>>>> >>
>>>>> >> +1
>>>>> >>
>>>>> >> Agree that people might be only interested in JIRA activities but
>>>>> not in the build.
>>>>> >>
>>>>> >>
>>>>> >> -Rui
>>>>> >>
>>>>> >> On Mon, Oct 15, 2018 at 10:27 AM Andrew Pilloud <
>>>>> apilloud@google.com> wrote:
>>>>> >>>
>>>>> >>> +1. A bunch of Jenkins spam goes to dev as well. Would be good to
>>>>> it all to a new list.
>>>>> >>>
>>>>> >>> Andrew
>>>>> >>>
>>>>> >>> On Mon, Oct 15, 2018 at 10:00 AM Colm O hEigeartaigh <
>>>>> coheigea@apache.org> wrote:
>>>>> >>>>
>>>>> >>>> As a rationale, some users might be interested in seeing JIRA
>>>>> activity but might not care about whether the build is broken or not :-)
>>>>> >>>>
>>>>> >>>> Colm.
>>>>> >>>>
>>>>> >>>> On Mon, Oct 15, 2018 at 5:56 PM Kenneth Knowles <ke...@apache.org>
>>>>> wrote:
>>>>> >>>>>
>>>>> >>>>> Separating this out from the Jira notification thread.
>>>>> >>>>>
>>>>> >>>>> Colm suggests that we also separate build notifications.
>>>>> >>>>>
>>>>> >>>>> WDYT?
>>>>> >>>>>
>>>>> >>>>> Kenn
>>>>> >>>>
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> --
>>>>> >>>> Colm O hEigeartaigh
>>>>> >>>>
>>>>> >>>> Talend Community Coder
>>>>> >>>> http://coders.talend.com
>>>>>
>>>>
>>>>

Re: [DISCUSS] Separate Jenkins notifications to a new mailing list

Posted by Kenneth Knowles <ke...@apache.org>.
OK, builds@beam.apache.org now exists.

I've opened https://github.com/apache/beam/pull/6775 to migrate but first
make the discussion more specific. There are three types of notifications
that are treated differently:

 - postcommits, etc, which were going to commits@
 - nightly release failures which were going to dev@
 - seed job failures which were going to dev@

They were different because they are different severity and frequency. I
don't use email for tracking their status anyhow, but would also happily
leave the dev@ jobs as-is if anyone does find it useful.

Kenn

On Tue, Oct 16, 2018 at 8:14 AM Kenneth Knowles <ke...@apache.org> wrote:

> Hi all,
>
> I moved pretty quickly and without adequate announcement of the
> establishment issues@ alias. Sorry if that caught anyone by surprise.
> This time I want to properly announce, but the support is pretty
> overwhelming so I'll just get the list set up as there's some latency on
> that. I'll let 72 hours pass before asking infra to flip the bit.
>
> Kenn
>
> On Tue, Oct 16, 2018 at 4:43 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> +1
>>
>> Regards
>> JB
>> Le 16 oct. 2018, à 12:46, Alexey Romanenko <ar...@gmail.com> a
>> écrit:
>>>
>>> +1
>>>
>>> On 16 Oct 2018, at 00:02, Chamikara Jayalath <ch...@google.com>
>>> wrote:
>>>
>>> +1 for new lists.
>>>
>>> Thanks,
>>> Cham
>>>
>>> On Mon, Oct 15, 2018 at 12:09 PM Ismaël Mejía <ie...@gmail.com> wrote:
>>>
>>>> +1
>>>> On Mon, Oct 15, 2018 at 8:14 PM Mikhail Gryzykhin <mi...@google.com>
>>>> wrote:
>>>> >
>>>> > +1 also suggested that in another thread.
>>>> >
>>>> > --Mikhail
>>>> >
>>>> > Have feedback?
>>>> >
>>>> >
>>>> > On Mon, Oct 15, 2018 at 11:10 AM Rui Wang <ru...@google.com> wrote:
>>>> >>
>>>> >> +1
>>>> >>
>>>> >> Agree that people might be only interested in JIRA activities but
>>>> not in the build.
>>>> >>
>>>> >>
>>>> >> -Rui
>>>> >>
>>>> >> On Mon, Oct 15, 2018 at 10:27 AM Andrew Pilloud <ap...@google.com>
>>>> wrote:
>>>> >>>
>>>> >>> +1. A bunch of Jenkins spam goes to dev as well. Would be good to
>>>> it all to a new list.
>>>> >>>
>>>> >>> Andrew
>>>> >>>
>>>> >>> On Mon, Oct 15, 2018 at 10:00 AM Colm O hEigeartaigh <
>>>> coheigea@apache.org> wrote:
>>>> >>>>
>>>> >>>> As a rationale, some users might be interested in seeing JIRA
>>>> activity but might not care about whether the build is broken or not :-)
>>>> >>>>
>>>> >>>> Colm.
>>>> >>>>
>>>> >>>> On Mon, Oct 15, 2018 at 5:56 PM Kenneth Knowles <ke...@apache.org>
>>>> wrote:
>>>> >>>>>
>>>> >>>>> Separating this out from the Jira notification thread.
>>>> >>>>>
>>>> >>>>> Colm suggests that we also separate build notifications.
>>>> >>>>>
>>>> >>>>> WDYT?
>>>> >>>>>
>>>> >>>>> Kenn
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> --
>>>> >>>> Colm O hEigeartaigh
>>>> >>>>
>>>> >>>> Talend Community Coder
>>>> >>>> http://coders.talend.com
>>>>
>>>
>>>

Re: [DISCUSS] Separate Jenkins notifications to a new mailing list

Posted by Kenneth Knowles <ke...@apache.org>.
Hi all,

I moved pretty quickly and without adequate announcement of the
establishment issues@ alias. Sorry if that caught anyone by surprise. This
time I want to properly announce, but the support is pretty overwhelming so
I'll just get the list set up as there's some latency on that. I'll let 72
hours pass before asking infra to flip the bit.

Kenn

On Tue, Oct 16, 2018 at 4:43 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:

> +1
>
> Regards
> JB
> Le 16 oct. 2018, à 12:46, Alexey Romanenko <ar...@gmail.com> a
> écrit:
>>
>> +1
>>
>> On 16 Oct 2018, at 00:02, Chamikara Jayalath <ch...@google.com>
>> wrote:
>>
>> +1 for new lists.
>>
>> Thanks,
>> Cham
>>
>> On Mon, Oct 15, 2018 at 12:09 PM Ismaël Mejía <ie...@gmail.com> wrote:
>>
>>> +1
>>> On Mon, Oct 15, 2018 at 8:14 PM Mikhail Gryzykhin <mi...@google.com>
>>> wrote:
>>> >
>>> > +1 also suggested that in another thread.
>>> >
>>> > --Mikhail
>>> >
>>> > Have feedback?
>>> >
>>> >
>>> > On Mon, Oct 15, 2018 at 11:10 AM Rui Wang <ru...@google.com> wrote:
>>> >>
>>> >> +1
>>> >>
>>> >> Agree that people might be only interested in JIRA activities but not
>>> in the build.
>>> >>
>>> >>
>>> >> -Rui
>>> >>
>>> >> On Mon, Oct 15, 2018 at 10:27 AM Andrew Pilloud <ap...@google.com>
>>> wrote:
>>> >>>
>>> >>> +1. A bunch of Jenkins spam goes to dev as well. Would be good to it
>>> all to a new list.
>>> >>>
>>> >>> Andrew
>>> >>>
>>> >>> On Mon, Oct 15, 2018 at 10:00 AM Colm O hEigeartaigh <
>>> coheigea@apache.org> wrote:
>>> >>>>
>>> >>>> As a rationale, some users might be interested in seeing JIRA
>>> activity but might not care about whether the build is broken or not :-)
>>> >>>>
>>> >>>> Colm.
>>> >>>>
>>> >>>> On Mon, Oct 15, 2018 at 5:56 PM Kenneth Knowles <ke...@apache.org>
>>> wrote:
>>> >>>>>
>>> >>>>> Separating this out from the Jira notification thread.
>>> >>>>>
>>> >>>>> Colm suggests that we also separate build notifications.
>>> >>>>>
>>> >>>>> WDYT?
>>> >>>>>
>>> >>>>> Kenn
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> --
>>> >>>> Colm O hEigeartaigh
>>> >>>>
>>> >>>> Talend Community Coder
>>> >>>> http://coders.talend.com
>>>
>>
>>

Re: [DISCUSS] Separate Jenkins notifications to a new mailing list

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1

Regards
JB

Le 16 oct. 2018 à 12:46, à 12:46, Alexey Romanenko <ar...@gmail.com> a écrit:
>+1
>
>> On 16 Oct 2018, at 00:02, Chamikara Jayalath <ch...@google.com>
>wrote:
>> 
>> +1 for new lists.
>> 
>> Thanks,
>> Cham
>> 
>> On Mon, Oct 15, 2018 at 12:09 PM Ismaël Mejía <iemejia@gmail.com
><ma...@gmail.com>> wrote:
>> +1
>> On Mon, Oct 15, 2018 at 8:14 PM Mikhail Gryzykhin <migryz@google.com
><ma...@google.com>> wrote:
>> >
>> > +1 also suggested that in another thread.
>> >
>> > --Mikhail
>> >
>> > Have feedback?
>> >
>> >
>> > On Mon, Oct 15, 2018 at 11:10 AM Rui Wang <ruwang@google.com
><ma...@google.com>> wrote:
>> >>
>> >> +1
>> >>
>> >> Agree that people might be only interested in JIRA activities but
>not in the build.
>> >>
>> >>
>> >> -Rui
>> >>
>> >> On Mon, Oct 15, 2018 at 10:27 AM Andrew Pilloud
><apilloud@google.com <ma...@google.com>> wrote:
>> >>>
>> >>> +1. A bunch of Jenkins spam goes to dev as well. Would be good to
>it all to a new list.
>> >>>
>> >>> Andrew
>> >>>
>> >>> On Mon, Oct 15, 2018 at 10:00 AM Colm O hEigeartaigh
><coheigea@apache.org <ma...@apache.org>> wrote:
>> >>>>
>> >>>> As a rationale, some users might be interested in seeing JIRA
>activity but might not care about whether the build is broken or not
>:-)
>> >>>>
>> >>>> Colm.
>> >>>>
>> >>>> On Mon, Oct 15, 2018 at 5:56 PM Kenneth Knowles <kenn@apache.org
><ma...@apache.org>> wrote:
>> >>>>>
>> >>>>> Separating this out from the Jira notification thread.
>> >>>>>
>> >>>>> Colm suggests that we also separate build notifications.
>> >>>>>
>> >>>>> WDYT?
>> >>>>>
>> >>>>> Kenn
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Colm O hEigeartaigh
>> >>>>
>> >>>> Talend Community Coder
>> >>>> http://coders.talend.com <http://coders.talend.com/>

Re: [DISCUSS] Separate Jenkins notifications to a new mailing list

Posted by Alexey Romanenko <ar...@gmail.com>.
+1

> On 16 Oct 2018, at 00:02, Chamikara Jayalath <ch...@google.com> wrote:
> 
> +1 for new lists.
> 
> Thanks,
> Cham
> 
> On Mon, Oct 15, 2018 at 12:09 PM Ismaël Mejía <iemejia@gmail.com <ma...@gmail.com>> wrote:
> +1
> On Mon, Oct 15, 2018 at 8:14 PM Mikhail Gryzykhin <migryz@google.com <ma...@google.com>> wrote:
> >
> > +1 also suggested that in another thread.
> >
> > --Mikhail
> >
> > Have feedback?
> >
> >
> > On Mon, Oct 15, 2018 at 11:10 AM Rui Wang <ruwang@google.com <ma...@google.com>> wrote:
> >>
> >> +1
> >>
> >> Agree that people might be only interested in JIRA activities but not in the build.
> >>
> >>
> >> -Rui
> >>
> >> On Mon, Oct 15, 2018 at 10:27 AM Andrew Pilloud <apilloud@google.com <ma...@google.com>> wrote:
> >>>
> >>> +1. A bunch of Jenkins spam goes to dev as well. Would be good to it all to a new list.
> >>>
> >>> Andrew
> >>>
> >>> On Mon, Oct 15, 2018 at 10:00 AM Colm O hEigeartaigh <coheigea@apache.org <ma...@apache.org>> wrote:
> >>>>
> >>>> As a rationale, some users might be interested in seeing JIRA activity but might not care about whether the build is broken or not :-)
> >>>>
> >>>> Colm.
> >>>>
> >>>> On Mon, Oct 15, 2018 at 5:56 PM Kenneth Knowles <kenn@apache.org <ma...@apache.org>> wrote:
> >>>>>
> >>>>> Separating this out from the Jira notification thread.
> >>>>>
> >>>>> Colm suggests that we also separate build notifications.
> >>>>>
> >>>>> WDYT?
> >>>>>
> >>>>> Kenn
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Colm O hEigeartaigh
> >>>>
> >>>> Talend Community Coder
> >>>> http://coders.talend.com <http://coders.talend.com/>


Re: [DISCUSS] Separate Jenkins notifications to a new mailing list

Posted by Chamikara Jayalath <ch...@google.com>.
+1 for new lists.

Thanks,
Cham

On Mon, Oct 15, 2018 at 12:09 PM Ismaël Mejía <ie...@gmail.com> wrote:

> +1
> On Mon, Oct 15, 2018 at 8:14 PM Mikhail Gryzykhin <mi...@google.com>
> wrote:
> >
> > +1 also suggested that in another thread.
> >
> > --Mikhail
> >
> > Have feedback?
> >
> >
> > On Mon, Oct 15, 2018 at 11:10 AM Rui Wang <ru...@google.com> wrote:
> >>
> >> +1
> >>
> >> Agree that people might be only interested in JIRA activities but not
> in the build.
> >>
> >>
> >> -Rui
> >>
> >> On Mon, Oct 15, 2018 at 10:27 AM Andrew Pilloud <ap...@google.com>
> wrote:
> >>>
> >>> +1. A bunch of Jenkins spam goes to dev as well. Would be good to it
> all to a new list.
> >>>
> >>> Andrew
> >>>
> >>> On Mon, Oct 15, 2018 at 10:00 AM Colm O hEigeartaigh <
> coheigea@apache.org> wrote:
> >>>>
> >>>> As a rationale, some users might be interested in seeing JIRA
> activity but might not care about whether the build is broken or not :-)
> >>>>
> >>>> Colm.
> >>>>
> >>>> On Mon, Oct 15, 2018 at 5:56 PM Kenneth Knowles <ke...@apache.org>
> wrote:
> >>>>>
> >>>>> Separating this out from the Jira notification thread.
> >>>>>
> >>>>> Colm suggests that we also separate build notifications.
> >>>>>
> >>>>> WDYT?
> >>>>>
> >>>>> Kenn
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Colm O hEigeartaigh
> >>>>
> >>>> Talend Community Coder
> >>>> http://coders.talend.com
>

Re: [DISCUSS] Separate Jenkins notifications to a new mailing list

Posted by Ismaël Mejía <ie...@gmail.com>.
+1
On Mon, Oct 15, 2018 at 8:14 PM Mikhail Gryzykhin <mi...@google.com> wrote:
>
> +1 also suggested that in another thread.
>
> --Mikhail
>
> Have feedback?
>
>
> On Mon, Oct 15, 2018 at 11:10 AM Rui Wang <ru...@google.com> wrote:
>>
>> +1
>>
>> Agree that people might be only interested in JIRA activities but not in the build.
>>
>>
>> -Rui
>>
>> On Mon, Oct 15, 2018 at 10:27 AM Andrew Pilloud <ap...@google.com> wrote:
>>>
>>> +1. A bunch of Jenkins spam goes to dev as well. Would be good to it all to a new list.
>>>
>>> Andrew
>>>
>>> On Mon, Oct 15, 2018 at 10:00 AM Colm O hEigeartaigh <co...@apache.org> wrote:
>>>>
>>>> As a rationale, some users might be interested in seeing JIRA activity but might not care about whether the build is broken or not :-)
>>>>
>>>> Colm.
>>>>
>>>> On Mon, Oct 15, 2018 at 5:56 PM Kenneth Knowles <ke...@apache.org> wrote:
>>>>>
>>>>> Separating this out from the Jira notification thread.
>>>>>
>>>>> Colm suggests that we also separate build notifications.
>>>>>
>>>>> WDYT?
>>>>>
>>>>> Kenn
>>>>
>>>>
>>>>
>>>> --
>>>> Colm O hEigeartaigh
>>>>
>>>> Talend Community Coder
>>>> http://coders.talend.com

Re: [DISCUSS] Separate Jenkins notifications to a new mailing list

Posted by Mikhail Gryzykhin <mi...@google.com>.
+1 also suggested that in another thread.

--Mikhail

Have feedback <http://go/migryz-feedback>?


On Mon, Oct 15, 2018 at 11:10 AM Rui Wang <ru...@google.com> wrote:

> +1
>
> Agree that people might be only interested in JIRA activities but not in
> the build.
>
>
> -Rui
>
> On Mon, Oct 15, 2018 at 10:27 AM Andrew Pilloud <ap...@google.com>
> wrote:
>
>> +1. A bunch of Jenkins spam goes to dev as well. Would be good to it all
>> to a new list.
>>
>> Andrew
>>
>> On Mon, Oct 15, 2018 at 10:00 AM Colm O hEigeartaigh <co...@apache.org>
>> wrote:
>>
>>> As a rationale, some users might be interested in seeing JIRA activity
>>> but might not care about whether the build is broken or not :-)
>>>
>>> Colm.
>>>
>>> On Mon, Oct 15, 2018 at 5:56 PM Kenneth Knowles <ke...@apache.org> wrote:
>>>
>>>> Separating this out from the Jira notification thread.
>>>>
>>>> Colm suggests that we also separate build notifications.
>>>>
>>>> WDYT?
>>>>
>>>> Kenn
>>>>
>>>
>>>
>>> --
>>> Colm O hEigeartaigh
>>>
>>> Talend Community Coder
>>> http://coders.talend.com
>>>
>>

Re: [DISCUSS] Separate Jenkins notifications to a new mailing list

Posted by Rui Wang <ru...@google.com>.
+1

Agree that people might be only interested in JIRA activities but not in
the build.


-Rui

On Mon, Oct 15, 2018 at 10:27 AM Andrew Pilloud <ap...@google.com> wrote:

> +1. A bunch of Jenkins spam goes to dev as well. Would be good to it all
> to a new list.
>
> Andrew
>
> On Mon, Oct 15, 2018 at 10:00 AM Colm O hEigeartaigh <co...@apache.org>
> wrote:
>
>> As a rationale, some users might be interested in seeing JIRA activity
>> but might not care about whether the build is broken or not :-)
>>
>> Colm.
>>
>> On Mon, Oct 15, 2018 at 5:56 PM Kenneth Knowles <ke...@apache.org> wrote:
>>
>>> Separating this out from the Jira notification thread.
>>>
>>> Colm suggests that we also separate build notifications.
>>>
>>> WDYT?
>>>
>>> Kenn
>>>
>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> Talend Community Coder
>> http://coders.talend.com
>>
>

Re: [DISCUSS] Separate Jenkins notifications to a new mailing list

Posted by Andrew Pilloud <ap...@google.com>.
+1. A bunch of Jenkins spam goes to dev as well. Would be good to it all to
a new list.

Andrew

On Mon, Oct 15, 2018 at 10:00 AM Colm O hEigeartaigh <co...@apache.org>
wrote:

> As a rationale, some users might be interested in seeing JIRA activity but
> might not care about whether the build is broken or not :-)
>
> Colm.
>
> On Mon, Oct 15, 2018 at 5:56 PM Kenneth Knowles <ke...@apache.org> wrote:
>
>> Separating this out from the Jira notification thread.
>>
>> Colm suggests that we also separate build notifications.
>>
>> WDYT?
>>
>> Kenn
>>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>

Re: [DISCUSS] Separate Jenkins notifications to a new mailing list

Posted by Colm O hEigeartaigh <co...@apache.org>.
As a rationale, some users might be interested in seeing JIRA activity but
might not care about whether the build is broken or not :-)

Colm.

On Mon, Oct 15, 2018 at 5:56 PM Kenneth Knowles <ke...@apache.org> wrote:

> Separating this out from the Jira notification thread.
>
> Colm suggests that we also separate build notifications.
>
> WDYT?
>
> Kenn
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com