Thanks for the updates so far everyone! Since support for the new Blink-based Table / SQL runner and fine-grained recovery are quite prominent features for 1.9.0, and developers involved in these topics have already expressed that these could make good use for another week, I think it definitely makes sense to postpone the feature freeze.
The new date for feature freeze and feature branch cut for 1.9.0 will be *July 5*. Please update on this thread if there are any further concerns! Cheers, Gordon On Tue, Jun 25, 2019 at 9:05 PM Chesnay Schepler <ches...@apache.org> wrote: > On the fine-grained recovery / batch scheduling side we could make good > use of another week. > Currently we are on track to have the _feature_ merged, but without > having done a great deal of end-to-end testing. > > On 25/06/2019 15:01, Kurt Young wrote: > > Hi Aljoscha, > > > > I also feel an additional week can make the remaining work more easy. At > > least > > we don't have to check in lots of commits in both branches (master & > > release-1.9). > > > > Best, > > Kurt > > > > > > On Tue, Jun 25, 2019 at 8:27 PM Aljoscha Krettek <aljos...@apache.org> > > wrote: > > > >> A few threads are converging around supporting the new Blink-based Table > >> API Runner/Planner. I think hitting the currently proposed feature > freeze > >> date is hard, if not impossible, and that the work would benefit from an > >> additional week to get everything in with good quality. > >> > >> What do the others involved in the topic think? > >> > >> Aljoscha > >> > >>> On 24. Jun 2019, at 19:42, Bowen Li <bowenl...@gmail.com> wrote: > >>> > >>> Hi Gordon, > >>> > >>> Thanks for driving this effort. > >>> > >>> Xuefu responded to the discussion thread [1] and I want to bring that > to > >>> our attention here: > >>> > >>> Hive integration depends on a few features that are actively developed. > >> If > >>> the completion of those features don't leave enough time for us to > >>> integrate, then our work can potentially go beyond the proposed date. > >>> > >>> Just wanted to point out such a dependency adds uncertainty. > >>> > >>> [1] > >>> > >> > http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Features-for-Apache-Flink-1-9-0-td28701.html > >>> On Thu, Jun 20, 2019 at 1:05 AM Tzu-Li (Gordon) Tai < > tzuli...@apache.org > >>> > >>> wrote: > >>> > >>>> Hi devs, > >>>> > >>>> Per the feature discussions for 1.9.0 [1], I hereby announce the > >> official > >>>> feature freeze for Flink 1.9.0 to be on June 28. A release feature > >> branch > >>>> for 1.9 will be cut following that date. > >>>> > >>>> We’re roughly one week away from this date, but please keep in mind > >> that we > >>>> still shouldn’t rush things. If you feel that there may be problems > with > >>>> this schedule for the things you are working on, please let us know > >> here. > >>>> Cheers, > >>>> Gordon > >>>> > >>>> [1] > >>>> > >>>> > >> > http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Features-for-Apache-Flink-1-9-0-td28701.html > >> > >
