Sure, sounds very good @Robert Metzger , @Hequn Cheng
@Dian Fu I will post the discussion of 1.6.4 later.
Best,
Jincheng
Robert Metzger 于2019年2月11日周一 下午8:46写道：
> Cool! Then let's do the release together. I haven't done it in a while, but
> we'll manage.
>
> Could you start a separate [DISC
Hi,
+1 on both 1.7.2 and 1.6.4. By then we can have a more stable release.
Best, Hequn
On Mon, Feb 11, 2019 at 8:46 PM Robert Metzger wrote:
> Cool! Then let's do the release together. I haven't done it in a while, but
> we'll manage.
>
> Could you start a separate [DISCUSS] thread for the 1
Cool! Then let's do the release together. I haven't done it in a while, but
we'll manage.
Could you start a separate [DISCUSS] thread for the 1.6.4 release?
On Mon, Feb 11, 2019 at 1:39 PM jincheng sun
wrote:
> Thank you for agreeing to release Flink 1.6.4. @Robert Metzger
> @Till Rohrmann
Thank you for agreeing to release Flink 1.6.4. @Robert Metzger
@Till Rohrmann !
I believe that users of Flink will also very much expect the release of
Flink 1.6.4.
I am very willing to contribute to the Flink community in any way. Of
course, it is a great honor to be able to do the release man
+1 to release 1.7.2.
Also +1 to the release 1.6.4 as there are already a few critical bug fixes in
the release-1.6 branch. It would be great to start a new thread for the vote of
release 1.6.4 to see if there are any critical bug fixes wanted to merged in
this release.
Regards,
Dian
> 在 2019年
+1 on a 1.6.4 release.
Jincheng, if you want to be the release manager, I'm happy to assist you
with my PMC powers :)
On Mon, Feb 11, 2019 at 1:24 PM Till Rohrmann wrote:
> Hi Jincheng,
>
> releasing a new bug fix release for the 1.6.x series is a really good idea
> since it already contains a
Hi Jincheng,
releasing a new bug fix release for the 1.6.x series is a really good idea
since it already contains a couple of important fixes. Do you want to be
the release manager for this release?
Cheers,
Till
On Mon, Feb 11, 2019 at 1:03 PM jincheng sun
wrote:
> Thanks Gordon to create the
Thanks Gordon to create the first release candidate for 1.7.2.
It has been a long time since the release of 1.6.3 (December 23, 2018).
There have been a lot of valuable bug fixes during this period. Do we need
to release 1.6.4?
Cheers,
Jincheng
Tzu-Li (Gordon) Tai 于2019年2月11日周一 下午5:06写道：
> Tha
Thanks. I'll proceed to create the first release candidate for 1.7.2 now
then.
On Mon, Feb 11, 2019 at 3:55 PM Till Rohrmann wrote:
> FLINK-10868 needs another round of reviews. At the moment, I cannot make
> any guarantees until when this will happen and therefore I would suggest to
> not block
FLINK-10868 needs another round of reviews. At the moment, I cannot make
any guarantees until when this will happen and therefore I would suggest to
not block 1.7.2 on this issue.
Cheers,
Till
On Mon, Feb 11, 2019 at 2:32 AM Tzu-Li (Gordon) Tai
wrote:
> Hi,
>
> Thanks for the replies.
>
> @Shuy
Hi,
Thanks for the replies.
@Shuyi, I prefer not to block release of 1.7.2 with FLINK-10868.
It does look like a major issue, but since it is already existing in older
versions while there are already some 1.7.x specific bug fixes already
pending to be released,
I would prefer to proceed with the
+1
@Gordon: There has been no further review of the PR that Shuyi linked
(https://github.com/apache/flink/pull/7356). Do you plan to block
1.7.2 on this or rather not?
– Ufuk
On Fri, Feb 8, 2019 at 10:35 PM Thomas Weise wrote:
>
> +1
>
>
> On Fri, Feb 8, 2019 at 6:14 AM jincheng sun
> wrote:
+1
On Fri, Feb 8, 2019 at 6:14 AM jincheng sun
wrote:
> +1 for starting Flink 1.7.2 release next week.
>
> Cheers,
> Jincheng
>
> Tzu-Li (Gordon) Tai 于2019年2月5日周二 下午11:32写道：
>
> > Hi Flink devs,
> >
> > What do you think about releasing Flink 1.7.2 soon?
> >
> > We already have some critical f
+1 for starting Flink 1.7.2 release next week.
Cheers,
Jincheng
Tzu-Li (Gordon) Tai 于2019年2月5日周二 下午11:32写道：
> Hi Flink devs,
>
> What do you think about releasing Flink 1.7.2 soon?
>
> We already have some critical fixes in the release-1.7 branch:
> - FLINK-11207: security vulnerability with cu
+1 for starting this release next week.
On Thu, Feb 7, 2019 at 11:50 AM Chesnay Schepler wrote:
> +1 to start the release next week, we've accumulated a nice set of
> changes and it's been more than a month since 1.7.1 came out.
>
> On 05.02.2019 16:32, Tzu-Li (Gordon) Tai wrote:
> > Hi Flink de
+1 to start the release next week, we've accumulated a nice set of
changes and it's been more than a month since 1.7.1 came out.
On 05.02.2019 16:32, Tzu-Li (Gordon) Tai wrote:
Hi Flink devs,
What do you think about releasing Flink 1.7.2 soon?
We already have some critical fixes in the releas
HI Gordon,
Thanks for bringing up the discussion. The following JIRA/PR is almost
there, and it's a major/critical issue that blocks us from upgrading to
Flink 1.6 or above in production. W/o this fix, a job might go into an
infinite resource acquirement loop without failing itself in YARN.
FLI
Hi Flink devs,
What do you think about releasing Flink 1.7.2 soon?
We already have some critical fixes in the release-1.7 branch:
- FLINK-11207: security vulnerability with currently used Apache
commons-compress version
- FLINK-11419: restore issue with StreamingFileSink
- FLINK-11436: restore is
18 matches
Mail list logo
