@Jark: Yes, I will request the creation of a mailing list! On Tue, Jul 23, 2019 at 4:48 PM Hugo Louro <hmclo...@gmail.com> wrote:
> +1 > > > On Jul 23, 2019, at 6:15 AM, Till Rohrmann <trohrm...@apache.org> wrote: > > > > Good idea Jark. +1 for the proposal. > > > > Cheers, > > Till > > > >> On Tue, Jul 23, 2019 at 1:59 PM Hequn Cheng <chenghe...@gmail.com> > wrote: > >> > >> Hi Jark, > >> > >> Good idea. +1! > >> > >>> On Tue, Jul 23, 2019 at 6:23 PM Jark Wu <imj...@gmail.com> wrote: > >>> > >>> Thank you all for your positive feedback. > >>> > >>> We have three binding +1s, so I think, we can proceed with this. > >>> > >>> Hi @Robert Metzger <rmetz...@apache.org> , could you create a request > to > >>> INFRA for the mailing list? > >>> I'm not sure if this needs a PMC permission. > >>> > >>> Thanks, > >>> Jark > >>> > >>> On Tue, 23 Jul 2019 at 16:42, jincheng sun <sunjincheng...@gmail.com> > >>> wrote: > >>> > >>>> +1 > >>>> > >>>> Robert Metzger <rmetz...@apache.org> 于2019年7月23日周二 下午4:01写道： > >>>> > >>>>> +1 > >>>>> > >>>>> On Mon, Jul 22, 2019 at 10:27 AM Biao Liu <mmyy1...@gmail.com> > >> wrote: > >>>>> > >>>>>> +1, make sense to me. > >>>>>> Mailing list seems to be a more "community" way. > >>>>>> > >>>>>> Timo Walther <twal...@apache.org> 于2019年7月22日周一 下午4:06写道： > >>>>>> > >>>>>>> +1 sounds good to inform people about instabilities or other > >> issues > >>>>>>> > >>>>>>> Regards, > >>>>>>> Timo > >>>>>>> > >>>>>>> > >>>>>>>> Am 22.07.19 um 09:58 schrieb Haibo Sun: > >>>>>>>> +1. Sounds good.Letting the PR creators know the build results > >> of > >>>> the > >>>>>>> master branch can help to determine more quickly whether Travis > >>>>> failures > >>>>>> of > >>>>>>> their PR are an exact failure or because of the instability of > >> test > >>>>> case. > >>>>>>> By the way, if the PR creator can abort their own Travis build, I > >>>> think > >>>>>> it > >>>>>>> can improve the efficient use of Travis resources (of course, > >> this > >>>>>>> discussion does not deal with this issue). > >>>>>>>> > >>>>>>>> > >>>>>>>> Best, > >>>>>>>> Haibo > >>>>>>>> At 2019-07-22 12:36:31, "Yun Tang" <myas...@live.com> wrote: > >>>>>>>>> +1 sounds good, more people could be encouraged to involve in > >>>> paying > >>>>>>> attention to failure commit. > >>>>>>>>> > >>>>>>>>> Best > >>>>>>>>> Yun Tang > >>>>>>>>> ________________________________ > >>>>>>>>> From: Becket Qin <becket....@gmail.com> > >>>>>>>>> Sent: Monday, July 22, 2019 9:44 > >>>>>>>>> To: dev <dev@flink.apache.org> > >>>>>>>>> Subject: Re: [DISCUSS] Setup a bui...@flink.apache.org > >> mailing > >>>> list > >>>>>>> for travis builds > >>>>>>>>> > >>>>>>>>> +1. Sounds a good idea to me. > >>>>>>>>> > >>>>>>>>> On Sat, Jul 20, 2019 at 7:07 PM Dian Fu < > >> dian0511...@gmail.com> > >>>>>> wrote: > >>>>>>>>> > >>>>>>>>>> Thanks Jark for the proposal, sounds reasonable for me. +1. > >>> This > >>>> ML > >>>>>>> could > >>>>>>>>>> be used for all the build notifications including master and > >>> CRON > >>>>>> jobs. > >>>>>>>>>> > >>>>>>>>>>> 在 2019年7月20日，下午2:55，Xu Forward <forwardxu...@gmail.com> 写道： > >>>>>>>>>>> > >>>>>>>>>>> +1 ,Thanks jark for the proposal. > >>>>>>>>>>> Best > >>>>>>>>>>> Forward > >>>>>>>>>>> > >>>>>>>>>>> Jark Wu <imj...@gmail.com> 于2019年7月20日周六 下午12:14写道： > >>>>>>>>>>> > >>>>>>>>>>>> Hi all, > >>>>>>>>>>>> > >>>>>>>>>>>> As far as I know, currently, email notifications of Travis > >>>> builds > >>>>>> for > >>>>>>>>>>>> master branch are sent to the commit author when a build > >> was > >>>> just > >>>>>>>>>> broken or > >>>>>>>>>>>> still is broken. And there is no email notifications for > >> CRON > >>>>>> builds. > >>>>>>>>>>>> > >>>>>>>>>>>> Recently, we are suffering from compile errors for > >> scala-2.12 > >>>> and > >>>>>>> java-9 > >>>>>>>>>>>> which are only ran in CRON jobs. So I'm figuring out a way > >> to > >>>> get > >>>>>>>>>>>> notifications of CRON builds (or all builds) to quick fix > >>>> compile > >>>>>>> errors > >>>>>>>>>>>> and failed cron tests. > >>>>>>>>>>>> > >>>>>>>>>>>> After reaching out to @Chesnay Schepler < > >> ches...@apache.org> > >>>>>> (thanks > >>>>>>>>>> for > >>>>>>>>>>>> the helping), I know that we are using a Slack channel to > >>>> receive > >>>>>> all > >>>>>>>>>>>> failed build notifications. However, IMO, email > >> notification > >>>>> might > >>>>>>> be a > >>>>>>>>>>>> better way than Slack channel to encourage more people to > >> pay > >>>>>>> attention > >>>>>>>>>> on > >>>>>>>>>>>> the builds. > >>>>>>>>>>>> > >>>>>>>>>>>> So I'm here to propose to setup a bui...@flink.apache.org > >>>>> mailing > >>>>>>> list > >>>>>>>>>> for > >>>>>>>>>>>> receiving build notifications. I also find that Beam has > >> such > >>>>>> mailing > >>>>>>>>>> list > >>>>>>>>>>>> too[1]. After we have such a mailing list, we can integrate > >>> it > >>>> to > >>>>>>> travis > >>>>>>>>>>>> according to the travis doc[2]. > >>>>>>>>>>>> > >>>>>>>>>>>> What do you think? Do we need a formal vote for this? > >>>>>>>>>>>> > >>>>>>>>>>>> Best and thanks, > >>>>>>>>>>>> Jark > >>>>>>>>>>>> > >>>>>>>>>>>> [1]: https://beam.apache.org/community/contact-us/ > >>>>>>>>>>>> [2]: > >>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > https://docs.travis-ci.com/user/notifications/#configuring-email-notifications > >>>>>>>>>>>> < > >>>>>>>>>>>> > >>>>>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > https://docs.travis-ci.com/user/notifications/#configuring-email-notifications > >>>>>>>>>>>> < > >>>>>>>>>>>> > >>>>>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > https://docs.travis-ci.com/user/notifications/#configuring-email-notifications > >>>>>>>>>> > >>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> >
