Hi,
I "sense a disturbance in the force" relating to the way we release Beam
with supported Flink versions. The current released version of Apache
Flink is 1.11.1, while we still support (at least up to Beam 2.24.0)
only version 1.10.1. There is tracking issue for 1.11. support [1], but
even if someone starts to work on this soon, it will probably not make
it to sooner release than 2.26.0, surely not before 2.25.0). I think
that the features included in newest Flink releases are pretty much
needed by our users, so I'd like to revive a somewhat left-over
discussion started in [2]. I think that we could be more aligned with
Flink's release is we created the following workflow:
- when a new Flink version is released, create a new branch for
flink-runner-<new_version>
- this new branch would depend on publihed SNAPSHOT version of the
not-yet-released version of Flink
- we would need a jenkins job that would periodically do builds
against new SNAPSHOTs and notify (some, volunteers welcome :))
committers about the status of the build
- this way, we might have people aware of incompatibilities, and
(pretty much) increase the chance, that the new runner branch would be
in shape to be able to switch from SNAPSHOT to release as soon as the
version of Beam gets released, merging the released version would mean
we create another branch for the new SNAPSHOT of Flink and repeat the
process
This workflow would rely on volunteer commiters (I'm one) that would be
willing to be notified about the failures and possibly fix them.
Looking forward for opinions, or alternative proposals to tackle this.
Jan
[1] https://issues.apache.org/jira/browse/BEAM-10612
[2]
https://lists.apache.org/thread.html/rfb5ac9d889d0e3f4400471de3c25000a15352bde879622c899d97581%40%3Cdev.beam.apache.org%3E
