If I may, think FLINK-10011 should be considered a blocker and included in
1.5.3 and a 1.4.3 release.
On Thu, Aug 16, 2018 at 3:09 AM Dominik Wosiński <wossyn@xxxxxxxxx> wrote:
+1, I agree that frequent releases are good for users.
Wysłane z aplikacji Poczta dla Windows 10
Od: Stefan Richter
Wysłano: czwartek, 16 sierpnia 2018 10:57
Temat: Re: [DISCUSS] Release Flink 1.5.3
+1 sounds good.
Am 16.08.2018 um 09:55 schrieb Piotr Nowojski <piotr@xxxxxxxxxxxxxxxxx>:
+1 from me
On 16 Aug 2018, at 09:40, Timo Walther <twalthr@xxxxxxxxxx> wrote:
Thank you for starting this discussion.
+1 for this
Am 16.08.18 um 09:27 schrieb vino yang:
Agree! This sounds very good.
Till Rohrmann <trohrmann@xxxxxxxxxx> 于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
On Thu, Aug 16, 2018 at 8:52 AM Chesnay Schepler <chesnay@xxxxxxxxxx>
I would actually start with the release process today unless anyone
On 16.08.2018 08:46, vino yang wrote:
I want to know when you plan to cut the branch.
Chesnay Schepler <c.schepler@xxxxxx> 于2018年8月16日周四 下午2:29写道：
it has been a little over 2 weeks since 1.5.2 was released, and
then a number of fixes were added to the release-1.5 that I think
should push to users.
Notable fixes, (among others) are FLINK-9969 which fixes a memory
when using batch, FLINK-10066 that reduces the memory print on the
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.