I agree it's better to take some extra time to ensure the quality of 2.10.0.
I've created a 2.7.1 branch and cherry-picked the relevant commits[1]. We could
start collecting other fixes in case there are any.
-Max
[1] https://github.com/apache/beam/pull/7687
On 30.01.19 20:57, Kenneth Knowles wrote:
Sounds good to me to target 2.7.1 and 2.10.0. I will have to re-roll RC2 after
confirming fixes for the latest blockers that were found. These are not
regressions from 2.9.0. But they seem severe enough that they are worth taking
an extra day or two, because 2.9.0 had enough problems that I would like to make
2.10.0 a more attractive upgrade target for users still on very old versions.
Kenn
On Wed, Jan 30, 2019 at 5:22 AM Maximilian Michels <[email protected]
<mailto:[email protected]>> wrote:
Hi everyone,
I know we are in the midst of releasing 2.10.0, but with the release process
taking its time I consider creating a patch release for this issue in the
FlinkRunner: https://jira.apache.org/jira/browse/BEAM-5386
Initially I thought it would be good to do a 2.9.1 release, but since we
have an
LTS version, we should probably do a 2.7.1 (LTS) release instead.
What do you think? I could only find one Fix Version 2.7.1 issue in JIRA:
https://jira.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20fixVersion%20%3D%202.7.1
Best,
Max
