I have pushed this fix to the release-1.5 branch:
https://issues.apache.org/jira/browse/FLINK-10566
Would be great if we could include it because it has been blocking some
pipelines on the Beam side.
Thanks,
Max
On 13.12.18 20:22, Chesnay Schepler wrote:
FLINK-11023: will not be fixed for 1.
FLINK-11023: will not be fixed for 1.5.6; this would take significantly
longer to implement, and TBH I'm not really keen on doing that for a
final bugfix release.
FLINK-7991: This is just a minor cleanup; the issue doesn't affect users
in any way. It is thus not particularly important to have fo
Hi,
I would be interested to try my hand at being the release manger for this.
There are currently still 5 in-progress issues [1], all except [2] with an
open PR.
Nico, Chesnay, Till: Can you please take a look and see if these can be
completed?
Thanks,
Thomas
[1]
https://issues.apache.org/ji
Thanks Till and my belated +1 for a final patch release :)
On Mon, Dec 10, 2018 at 5:47 AM Till Rohrmann wrote:
> Thanks for the feedback! I conclude that the community is in favour of a
> last 1.5.6 release. I'll try to make the arrangements in the next two
> weeks.
>
> Cheers,
> Till
>
> On Mo
Thanks for the feedback! I conclude that the community is in favour of a
last 1.5.6 release. I'll try to make the arrangements in the next two weeks.
Cheers,
Till
On Mon, Dec 10, 2018 at 2:40 AM jincheng sun
wrote:
> +1. There are incompatible improvements between 1.5.x and 1.6/1.7, so many
> 1
+1. There are incompatible improvements between 1.5.x and 1.6/1.7, so many
1.5.x users may not be willing to upgrade to 1.6 or 1.7 due to migration
costs, so it makes sense to creating last bug fix release for 1.5 branch.
Bests,
Jincheng
Jeff Zhang 于2018年12月10日周一 上午9:24写道：
> +1, I think very fe
+1, I think very few people would use 1.6 or 1.7 in their production in
near future, so I expect they would use 1.5 in production for a long
period，it makes sense to provide a stable version for production usage.
Ufuk Celebi 于2018年12月9日周日 下午6:07写道：
> +1. This seems reasonable to me. Since the fi
+1. This seems reasonable to me. Since the fixes are already in and
also part of other releases, the release overhead should be
manageable.
@Vino: I agree with your assessment.
@Qi: As Till mentioned, the official project guideline is to support
the last two minor releases, e.g. currently 1.7 and
Hi Till,
Does Flink has an agreement on how long will a major version be supported? Some
companies may need a long time to upgrade Flink major versions in production.
If Flink terminates support for a major version too quickly, it may be a
concern for companies.
Best,
Qi
> On Dec 8, 2018, at
Hi Till,
I think it makes sense to release a bug fix version (especially some
serious bug fixes) for flink 1.5.
Consider that some companies' production environments are more cautious
about upgrading large versions.
I think some organizations are still using 1.5.x or even 1.4.x.
Best,
Vino
Till
Dear community,
I wanted to reach out to you and discuss whether we should release a last
bug fix release for the 1.5 branch.
Since we have already released Flink 1.7.0, we only need to support the
1.6.x and 1.7.x branches (last two major releases). However, the current
release-1.5 branch contain
11 matches
Mail list logo
