+1 for 1.6.4

On Tue, Feb 12, 2019 at 6:18 PM Thomas Weise <t...@apache.org> wrote:

> +1 for making it the final 1.6.x release
>
>
> On Tue, Feb 12, 2019 at 7:10 AM Chesnay Schepler <ches...@apache.org>
> wrote:
>
> > I assume we will treat this as the last bugfix release in the 1.6 series?
> >
> > On 12.02.2019 10:00, jincheng sun wrote:
> > > Hi Flink devs,
> > >
> > > 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.
> > > What do you think about releasing Flink 1.6.4 soon?
> > >
> > > We already have some critical fixes in the release-1.6 branch(such as):
> > >
> > > - FLINK-11235: Solve Elasticsearch connector thread leaks
> > > - FLINK-11207: security vulnerability with currently used
> > > Apachecommons-compress version
> > > - FLINK-10761: do not acquire lock for getAllVariables
> > > - FLINK-10761: potential deadlock with metrics system
> > > - FLINK-11140: fix empty child path check in Buckets
> > > - FLINK-10774: connection leak in FlinkKafkaConsumer
> > > - FLINK-10848: problem with resource allocation in YARN mode
> > > - FLINK-11419: restore issue with StreamingFileSink
> > > - FLINK-10774: connection leak in FlinkKafkaConsumer
> > >
> > > Please let me know what you think. Ideally, we can kick off the release
> > > vote for the first RC early next week.
> > >
> > > I have a preliminary analysis of the JIRAs on 1.6.4. There are
> currently
> > 4
> > > in progress, and there are 23 need to do.
> > > I have write the Google doc
> > > <
> >
> https://docs.google.com/document/d/1ESMrCkLT_Lf4L1Mw1nEu2c0yqlM_MzMRpjAHC0G3Ln0/edit?usp=sharing
> > >
> > > for how to processing of these JIRAs. Welcome to comment in the email
> or
> > in
> > > the Google doc
> > > <
> >
> https://docs.google.com/document/d/1ESMrCkLT_Lf4L1Mw1nEu2c0yqlM_MzMRpjAHC0G3Ln0/edit?usp=sharing
> > >
> > > .
> > >
> > > If there are some other critical fixes for 1.6.4 that are almost
> > completed
> > > (already have a PR opened and review is in progress),
> > > please let me know here by the end of this week.
> > >
> > > Cheers,
> > > Jincheng
> > >
> >
> >
>

Reply via email to