Hi Jincheng, Thanks for kicking this discussion off!
+1 to the 1.8.3 release as it would be nice to have these important fixes and also two months have passed since the last release. Besides, I wonder if I can be the release manager of 1.8.3 or work with you together @Jincheng? It's always exciting to help the community as much as possible. Best, Hequn On Sat, Nov 9, 2019 at 12:34 PM Dian Fu <dian0511...@gmail.com> wrote: > Hi Jincheng, > > Thanks a lot for bringing up this discussion. +1 for releasing 1.8.3. > > Regards, > Dian > > On Sat, Nov 9, 2019 at 12:11 PM jincheng sun <sunjincheng...@gmail.com> > wrote: > > > Hi Flink devs, > > > > It has been more than 2 months since the 1.8.2 released. So, What do you > > think about releasing Flink 1.8.3 soon? > > > > We already have many important bug fixes in the release-1.8 branch (29 > > resolved issues). > > > > Most notable fixes are: > > > > - FLINK-14010 Dispatcher & JobManagers don't give up leadership when AM > is > > shut down > > - FLINK-14315 NPE with JobMaster.disconnectTaskManager > > - FLINK-12848 Method equals() in RowTypeInfo should consider fieldsNames > > - FLINK-12342 Yarn Resource Manager Acquires Too Many Containers > > - FLINK-14589 Redundant slot requests with the same AllocationID leads to > > inconsistent slot table > > > > Furthermore, the following critical issues is in progress, maybe we can > > wait for it if it is not too much effort. > > > > - FLINK-13184 Starting a TaskExecutor blocks the YarnResourceManager's > main > > thread > > > > Please let me know what you think? > > > > Best, > > Jincheng > > >