Hi all,

INFRA moved the github and jira notifications to issues.

If you want to receive all notifications, please subscribe to
iss...@bookkeeper.apache.org mailing list.

http://bookkeeper.apache.org/community/mailing-lists/

- Sijie

On Sun, Aug 13, 2017 at 11:34 PM, Sijie Guo <guosi...@gmail.com> wrote:

> Configured all the jenkins job to send notifications to
> iss...@bookkeeper.apache.org.
>
> Filed https://issues.apache.org/jira/browse/INFRA-14863 for sending jira
> and github notifications to iss...@bookkeeper.apache.org.
>
> If you want to receive all the notifications, please subscribe to
> iss...@bookkeeper.apache.org (by sending email to
> issues-subscr...@bookkeeper.apache.org) and follow the instructions.
>
> I also created a github issue for updating the `mailing list` page:
> https://github.com/apache/bookkeeper/issues/443
>
> - Sijie
>
> On Sun, Aug 13, 2017 at 11:19 PM, Sijie Guo <guosi...@gmail.com> wrote:
>
>> Since there is no complaints about sending the notifications to issues@,
>> I am going to proceed the next steps.
>>
>> - Sijie
>>
>> On Fri, Aug 11, 2017 at 4:21 PM, JV Jujjuri <vjujj...@salesforce.com>
>> wrote:
>>
>>> Thanks a lot Sijie.
>>>
>>> On Fri, Aug 11, 2017 at 2:31 PM, Sijie Guo <guosi...@gmail.com> wrote:
>>>
>>>> okay. if there is no complaints for sending the notifications of
>>>> 'jenkins', 'jira' and 'git' to issues@ mailing list by end of this
>>>> week, I will create an INFRA ticket for that.
>>>>
>>>> - Sijie
>>>>
>>>> On Fri, Aug 11, 2017 at 12:32 AM, Enrico Olivelli <eolive...@gmail.com>
>>>> wrote:
>>>>
>>>>> Il ven 11 ago 2017, 02:07 Jia Zhai <zhaiji...@gmail.com> ha scritto:
>>>>>
>>>>> > ```
>>>>> > We can possibly move "jekins", "jira" and "git" related emails to a
>>>>> > separate mailing list like issues@. for the mention emails, you
>>>>> might just
>>>>> > create a filter rule to categorize them.
>>>>> > ```
>>>>> > 👍
>>>>> > This seems enough to me.
>>>>> >
>>>>> >
>>>>> > On Fri, Aug 11, 2017 at 7:01 AM, Sijie Guo <guosi...@gmail.com>
>>>>> wrote:
>>>>> >
>>>>> > > I think when you were mentioned (tagged) in github. You will
>>>>> receive an
>>>>> > > email like below: You email and a "Mention <
>>>>> ment...@noreply.github.com"
>>>>> > > email address will be cced. You can use that as a condition to
>>>>> filter out
>>>>> > > your emails.
>>>>> > >
>>>>> > > from: Venkateswararao Jujjuri (JV) <notificati...@github.com>
>>>>> > > reply-to: apache/bookkeeper <reply+00129547204652a3e682947
>>>>> > > 62db658ae96914785abda9c8892cf0000000115a4415392a169ce0ecd367
>>>>> > > 0...@reply.github.com>
>>>>> > > to: apache/bookkeeper <bookkee...@noreply.github.com>
>>>>> > > cc: Sijie Guo <guosi...@gmail.com>,
>>>>> > > Mention <ment...@noreply.github.com>
>>>>> > >
>>>>> > > Here is my filter - just as an example: (also attached a gmail
>>>>> filter
>>>>> > file
>>>>> > > in this email. if you want to use it, change the rule for
>>>>> > > bookkeeper/mention to use your email :) )
>>>>> > >
>>>>> > >
>>>>> > > from:(-(g...@git.apache.org OR jenk...@builds.apache.org OR
>>>>> > j...@apache.org))
>>>>> > > to:(dev@bookkeeper.apache.org) => bookkeeper/dev
>>>>> > > from:(g...@git.apache.org) to:(dev@bookkeeper.apache.org) =>
>>>>> > bookkeeper/git
>>>>> > > from:(jenk...@builds.apache.org) to:(dev@bookkeeper.apache.org) =>
>>>>> > > bookkeeper/jenkins
>>>>> > > from:(j...@apache.org) to:(dev@bookkeeper.apache.org) =>
>>>>> bookkeeper/jira
>>>>> > > to:(bookkee...@noreply.github.com, ment...@noreply.github.com,
>>>>> > > guosi...@gmail.com) => bookkeeper/mention (all the notifications
>>>>> when
>>>>> > you
>>>>> > > were tagged on github)
>>>>> > >
>>>>> > >
>>>>> > > We can possibly move "jekins", "jira" and "git" related emails to a
>>>>> > > separate mailing list like issues@. for the mention emails, you
>>>>> might
>>>>> > > just create a filter rule to categorize them.
>>>>> > >
>>>>> > > Thoughts?
>>>>> > >
>>>>> > > - Sijie
>>>>> > >
>>>>> > >
>>>>> > > On Thu, Aug 10, 2017 at 2:37 PM, Venkateswara Rao Jujjuri <
>>>>> > > jujj...@gmail.com> wrote:
>>>>> > >
>>>>> > >> Also if there is a way, I would like github to send email to the
>>>>> tagged
>>>>> > >> person in addition to alias.
>>>>> > >> Not sure if github can support that, that way tagged person can
>>>>> get
>>>>> > >> quicker
>>>>> > >> attention instead of processing
>>>>> > >> every email on the issues@ or dev@ list. Not sure if github can
>>>>> support
>>>>> > >> that feature.
>>>>> > >>
>>>>> > >> JV
>>>>> > >>
>>>>> > >> On Thu, Aug 10, 2017 at 2:34 PM, Sijie Guo <guosi...@gmail.com>
>>>>> wrote:
>>>>> > >>
>>>>> > >> > Hi all,
>>>>> > >> >
>>>>> > >> > JV and me had a short discussion about emails in the dev
>>>>> mailing list.
>>>>> > >> Most
>>>>> > >> > of the emails are coming from github notifications. If you
>>>>> don't have
>>>>> > >> > filters setup correctly, it might be annoying and hard to
>>>>> follow the
>>>>> > >> real
>>>>> > >> > discussion happening in dev@.
>>>>> > >> >
>>>>> > >> > Shall we consider moving all the github notifications to other
>>>>> mailing
>>>>> > >> > lists? like issues@? Any thoughts?
>>>>> >
>>>>>
>>>>> Ok to me, I think that most people are not interested in all the
>>>>> things.
>>>>>
>>>>> I would encourage every committer to follow every tool because we
>>>>> should
>>>>> keep  eyes open on any regression, the earlier we see the earlier we
>>>>> can
>>>>> fix it
>>>>>
>>>>> Enrico
>>>>>
>>>>> >> >
>>>>> > >> > - Sijie
>>>>> > >> >
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>> > >> --
>>>>> > >> Jvrao
>>>>> > >> ---
>>>>> > >> First they ignore you, then they laugh at you, then they fight
>>>>> you, then
>>>>> > >> you win. - Mahatma Gandhi
>>>>> > >>
>>>>> > >
>>>>> > >
>>>>> >
>>>>> --
>>>>>
>>>>>
>>>>> -- Enrico Olivelli
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Venkateswararao Jujjuri (JV)                      2035 NW Cornelius Pass
>>> Rd
>>> Architect, Sr. Director                                  Hillsboro, OR
>>> 97124
>>> Storage Cloud                                             971 270 6748
>>> <(971)%20270-6748>
>>> Infrastructure Engineering
>>> vjujj...@salesforce.com
>>>
>>
>>
>

Reply via email to