+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
