Hi Robert, Regarding FLINK-10776 - Update migration tests for Flink 1.7: There's still one last test class that needs to be migrated (progress reflected in the list of subtasks of FLINK-10776), and we definitely should still fix that before releasing 1.8.0 to ensure backwards compatibility of savepoints.
However, I don't think it should block the upcoming feature freeze, as it is test extension which can be resolved as part of the testing phase. Cheers, Gordon On Mon, Feb 18, 2019 at 4:44 PM Robert Metzger <rmetz...@apache.org> wrote: > I'm not involved enough with the development to say whether end of this > week is a realistic deadline. > But I see that it makes sense to release 1.8 soon, if it is blocking the > Table API refactoring. > > There are 5 blockers assigned to the 1.8.0 release: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20priority%20%3D%20Blocker%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%201.8.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > > These are the issues and my thoughts: > > - FLINK-11537 <https://issues.apache.org/jira/browse/FLINK-11537> | > ExecutionGraph does not reach terminal state when JobMaster lost leadership > | --> We should address this before the release! > - FLINK-11121 <https://issues.apache.org/jira/browse/FLINK-11121> | Check > and update licensing notes for Aliyun FS [FLINK-10865] | --> We should > address this before the release! > - FLINK-11249 | FlinkKafkaProducer011 can not be migrated to > FlinkKafkaProducer | --> According to the latest comment on the PR, it > seems that there is agreement to not include the fix into the 1.8 release. > I propose to remove the JIRA from the 1.8 release > - FLINK-11541 <https://issues.apache.org/jira/browse/FLINK-11541> | Heavy > deployment E2E test failed on Travis | --> This issue has not been > analyzed. > - FLINK-10776 | Update migration tests for Flink 1.7 | --> @Gordon What's > the status here? > > > > On Mon, Feb 18, 2019 at 8:46 AM Hequn Cheng <chenghe...@gmail.com> wrote: > > > Thanks for planning on the 1.8 release. +1 for cutting the release branch > > soon. > > > > As Stephan and Jincheng said, the refactoring of Table API may block the > > release. Fortunately, some issues have already been merged into the > master, > > for example, deprecate methods in TableEnvironment and Table. And some > > others are under review, so hopefully, we can cut the branch on Feb 22. > > Hoping to have a chance to help on the 1.8 release. :-) > > > > Best, Hequn > > > > > > On Wed, Feb 13, 2019 at 5:11 PM jincheng sun <sunjincheng...@gmail.com> > > wrote: > > > > > Thanks for bring up the discuss of 1.8 release Aljoscha ! > > > > > > +1 for feature freeze for 1.8 release soon. > > > > > > As Stephan mentioned above, Table API refactoring work is blocked on a > > > release. > > > The expects changes of deprecated(in 1.8) APIs (Such as: > > > ExternalCatalogTable#builder(), new Table(..) ) in the TableAPI > > refactoring > > > work has been merged into the Master. So from the points of my view, I > > > hope cutting of the 1.8 release branch ASAP. :-) > > > > > > Of course, I agree that we shouldn’t rush things. > > > > > > Best, > > > Jincheng > > > > > > > > > > > > > > > > > > > > > Stephan Ewen <se...@apache.org> 于2019年2月13日周三 上午2:00写道： > > > > > > > +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 > > > > > > > > > >
