Thank you for starting this discussion.
+1 for this
Regards,
Timo
Am 16.08.18 um 09:27 schrieb vino yang:
Agree! This sounds very good.
Till Rohrmann <trohrm...@apache.org> 于2018年8月16日周四 下午3:14写道：
+1 for starting the release process 1.5.3 immediately. We can always
create another bug fix release afterwards. I think the more often we
release the better it is for our users, because they receive incremental
improvements faster.
Cheers,
Till
On Thu, Aug 16, 2018 at 8:52 AM Chesnay Schepler <ches...@apache.org>
wrote:
I would actually start with the release process today unless anyone
objects.
On 16.08.2018 08:46, vino yang wrote:
Hi Chesnay,
+1
I want to know when you plan to cut the branch.
Thanks, vino.
Chesnay Schepler <c.schep...@web.de> 于2018年8月16日周四 下午2:29写道：
Hello everyone,
it has been a little over 2 weeks since 1.5.2 was released, and since
then a number of fixes were added to the release-1.5 that I think we
should push to users.
Notable fixes, (among others) are FLINK-9969 which fixes a memory leak
when using batch, FLINK-10066 that reduces the memory print on the JM
for long-running jobs or FLINK-10070 that reverses a regression
introduced in 1.5.2 due to which Flink could not be compiled with
certain maven versions.
I would of course volunteer as Release Manager.
