Hi, +1 on both 1.7.2 and 1.6.4. By then we can have a more stable release.
Best, Hequn On Mon, Feb 11, 2019 at 8:46 PM Robert Metzger <rmetz...@apache.org> wrote: > Cool! Then let's do the release together. I haven't done it in a while, but > we'll manage. > > Could you start a separate [DISCUSS] thread for the 1.6.4 release? > > On Mon, Feb 11, 2019 at 1:39 PM jincheng sun <sunjincheng...@gmail.com> > wrote: > > > Thank you for agreeing to release Flink 1.6.4. @Robert Metzger > > <rmetz...@apache.org> @Till Rohrmann <trohrm...@apache.org> ! > > I believe that users of Flink will also very much expect the release of > > Flink 1.6.4. > > I am very willing to contribute to the Flink community in any way. Of > > course, it is a great honor to be able to do the release manager of Flink > > 1.6.4. I am willing to make the best effort for the release of Flinjk > 1.6.4. > > > > Thanks, > > Jincheng > > > > Robert Metzger <rmetz...@apache.org> 于2019年2月11日周一 下午8:30写道： > > > >> +1 on a 1.6.4 release. > >> > >> Jincheng, if you want to be the release manager, I'm happy to assist you > >> with my PMC powers :) > >> > >> On Mon, Feb 11, 2019 at 1:24 PM Till Rohrmann <trohrm...@apache.org> > >> wrote: > >> > >> > Hi Jincheng, > >> > > >> > releasing a new bug fix release for the 1.6.x series is a really good > >> idea > >> > since it already contains a couple of important fixes. Do you want to > be > >> > the release manager for this release? > >> > > >> > Cheers, > >> > Till > >> > > >> > On Mon, Feb 11, 2019 at 1:03 PM jincheng sun < > sunjincheng...@gmail.com> > >> > wrote: > >> > > >> > > Thanks Gordon to create the first release candidate for 1.7.2. > >> > > > >> > > It has been a long time since the release of 1.6.3 (December 23, > >> 2018). > >> > > There have been a lot of valuable bug fixes during this period. Do > we > >> > need > >> > > to release 1.6.4? > >> > > > >> > > Cheers, > >> > > Jincheng > >> > > > >> > > Tzu-Li (Gordon) Tai <tzuli...@apache.org> 于2019年2月11日周一 下午5:06写道： > >> > > > >> > > > Thanks. I'll proceed to create the first release candidate for > 1.7.2 > >> > now > >> > > > then. > >> > > > > >> > > > On Mon, Feb 11, 2019 at 3:55 PM Till Rohrmann < > trohrm...@apache.org > >> > > >> > > > wrote: > >> > > > > >> > > > > FLINK-10868 needs another round of reviews. At the moment, I > >> cannot > >> > > make > >> > > > > any guarantees until when this will happen and therefore I would > >> > > suggest > >> > > > to > >> > > > > not block 1.7.2 on this issue. > >> > > > > > >> > > > > Cheers, > >> > > > > Till > >> > > > > > >> > > > > On Mon, Feb 11, 2019 at 2:32 AM Tzu-Li (Gordon) Tai < > >> > > tzuli...@apache.org > >> > > > > > >> > > > > wrote: > >> > > > > > >> > > > >> Hi, > >> > > > >> > >> > > > >> Thanks for the replies. > >> > > > >> > >> > > > >> @Shuyi, I prefer not to block release of 1.7.2 with > FLINK-10868. > >> > > > >> It does look like a major issue, but since it is already > >> existing in > >> > > > >> older versions while there are already some 1.7.x specific bug > >> fixes > >> > > > >> already pending to be released, > >> > > > >> I would prefer to proceed with the 1.7.2 release as soon as > >> > possible. > >> > > > >> > >> > > > >> @Till, since you was part of reviewing 1.7.2 before, what's > your > >> > take > >> > > on > >> > > > >> the status of the PR? > >> > > > >> > >> > > > >> Cheers, > >> > > > >> Gordon > >> > > > >> > >> > > > >> On Sat, Feb 9, 2019 at 3:30 PM Ufuk Celebi <u...@apache.org> > >> wrote: > >> > > > >> > >> > > > >>> +1 > >> > > > >>> > >> > > > >>> @Gordon: There has been no further review of the PR that Shuyi > >> > linked > >> > > > >>> (https://github.com/apache/flink/pull/7356). Do you plan to > >> block > >> > > > >>> 1.7.2 on this or rather not? > >> > > > >>> > >> > > > >>> – Ufuk > >> > > > >>> > >> > > > >>> On Fri, Feb 8, 2019 at 10:35 PM Thomas Weise <t...@apache.org> > >> > wrote: > >> > > > >>> > > >> > > > >>> > +1 > >> > > > >>> > > >> > > > >>> > > >> > > > >>> > On Fri, Feb 8, 2019 at 6:14 AM jincheng sun < > >> > > > sunjincheng...@gmail.com> > >> > > > >>> > wrote: > >> > > > >>> > > >> > > > >>> > > +1 for starting Flink 1.7.2 release next week. > >> > > > >>> > > > >> > > > >>> > > Cheers, > >> > > > >>> > > Jincheng > >> > > > >>> > > > >> > > > >>> > > Tzu-Li (Gordon) Tai <tzuli...@apache.org> 于2019年2月5日周二 > >> > > 下午11:32写道： > >> > > > >>> > > > >> > > > >>> > > > Hi Flink devs, > >> > > > >>> > > > > >> > > > >>> > > > What do you think about releasing Flink 1.7.2 soon? > >> > > > >>> > > > > >> > > > >>> > > > We already have some critical fixes in the release-1.7 > >> > branch: > >> > > > >>> > > > - FLINK-11207: security vulnerability with currently > used > >> > > Apache > >> > > > >>> > > > commons-compress version > >> > > > >>> > > > - FLINK-11419: restore issue with StreamingFileSink > >> > > > >>> > > > - FLINK-11436: restore issue with Flink's AvroSerializer > >> > > > >>> > > > - FLINK-10761: potential deadlock with metrics system > >> > > > >>> > > > - FLINK-10774: connection leak in FlinkKafkaConsumer > >> > > > >>> > > > - FLINK-10848: problem with resource allocation in YARN > >> mode > >> > > > >>> > > > > >> > > > >>> > > > Please let me know what you think. Ideally, we can kick > >> off > >> > the > >> > > > >>> release > >> > > > >>> > > > vote for the first RC early next week. > >> > > > >>> > > > If there are some other critical fixes for 1.7.2 that > are > >> > > almost > >> > > > >>> > > completed > >> > > > >>> > > > (already have a PR opened and review is in progress), > >> please > >> > > let > >> > > > >>> me know > >> > > > >>> > > > here by the end of the week to account for it for the > >> 1.7.2 > >> > > > >>> release. > >> > > > >>> > > > > >> > > > >>> > > > Cheers, > >> > > > >>> > > > Gordon > >> > > > >>> > > > > >> > > > >>> > > > >> > > > >>> > >> > > > >> > >> > > > > >> > > > >> > > >> > > >
