+1 for feature freeze on Feb 22. I focus on two features which are expected to be covered in 1.8 release before. The broadcast serialization improvement [1] only left one PR which would be done with expectation. The pluggable shuffle manager [2] might not catch up with this time, but I think it is not the blocker for the release.
[1] https://issues.apache.org/jira/browse/FLINK-10745 [2] https://issues.apache.org/jira/browse/FLINK-10653 Best, Zhijiang ------------------------------------------------------------------ From:Ufuk Celebi <u...@apache.org> Send Time:2019年2月13日(星期三) 16:01 To:dev <dev@flink.apache.org> Subject:Re: [DISCUSS] Releasing Flink 1.8 / Feature Freeze +1 for Feb 22. Thanks for being the release manager. – Ufuk On Tue, Feb 12, 2019 at 7:00 PM Stephan Ewen <se...@apache.org> wrote: > > +1 for doing a 1.8 release soon. > > Some of the Table API refactoring work is blocked on a release (assuming we > want one release to deprecate some functions before dropping them. > > On Tue, Feb 12, 2019 at 11:03 AM Aljoscha Krettek <aljos...@apache.org> > wrote: > > > Hi All, > > > > In reference to a recent mail by Ufuk [1] and because it has been a while > > since the last Flink release we should start thinking about a Flink 1.8 > > release. We’re actually a bit behind the cadence but I think we still > > shouldn’t rush things. I’m hereby proposing myself as release manager for > > Flink 1.8 and I also want to suggest February 22 as the date for feature > > freeze and cutting of the 1.8 release branch. This is quite soon but still > > gives us two weeks to work on things. > > > > What do you think? > > > > Best, > > Aljoscha > > > > [1] > > https://lists.apache.org/thread.html/423164e045c3c206f2b8d5c061be7055ef4bc3fd880c28a862ef5d8c@%3Cdev.flink.apache.org%3E
