Probably. I was hesitant to move to 1.5 without significant testing, as we
run in standalone mode and 1.5 introduced significant changes as a result
of FLIP-6. But if the community hasn't seen major regressions in 1.5
running in legacy mode, then that may be feasible.
On Mon, Sep 17, 2018 at 1:41 AM Till Rohrmann <
[hidden email]> wrote:
> Would you be able to upgrade to Flink 1.5.4 or 1.6.1 using Flink's legacy
> mode @Elias? The legacy mode should have the same behaviour as Flink
> 1.4-SNAPSHOT and thus a potential Flink 1.4.3.
>
> I'm a bit hesitant to make another 1.4 release, because in 1.4 we didn't
> have many automated e2e tests. Consequently, the release process would
> require a considerable community effort for testing in order to make sure
> that the release is properly working.
>
> What do you think?
>
> Cheers,
> Till
>
> On Fri, Sep 14, 2018 at 7:10 PM Elias Levy <
[hidden email]>
> wrote:
>
> > Any chance we may see a 1.4.3 release with the ZK fixes?
> >
> > On Fri, Sep 14, 2018 at 8:29 AM Till Rohrmann <
[hidden email]>
> > wrote:
> >
> > > Hi everyone,
> > >
> > > it has already been a couple of weeks since we released Flink 1.5.3 and
> > > Flink 1.6.0. In both release branches are important bug fixes from
> which
> > > our users can benefit (1.5.4: 23 resolved issues, 1.6.1: 60 resolved
> > > issues). Therefore, I propose to create the next bug fix release for
> > Flink
> > > 1.5 and 1.6.
> > >
> > > Most notable fixes are: FLINK-10255 (Standby Dispatcher locks submitted
> > > JobGraphs), FLINK-10193 (Use proper timeout when triggering savepoint),
> > > FLINK-10314 (ExecutionGraph creation can be blocking) and
> FLINK-10011(Old
> > > jobs sometimes get resurrected during HA failover).
> > >
> > > I would of course volunteer as release manager and kick off the release
> > > process once FLINK-10314 has been merged. What do you think?
> > >
> > > Cheers,
> > > Till
> > >
> >
>
Locked
