On Fri, May 26, 2017 at 3:59 PM, Robert Metzger <rmetz...@apache.org> wrote:
> Thanks a lot. > > JIRA also shows me 0 open blockers :) > I'll then kick off the RC3 creation process. > > On Fri, May 26, 2017 at 10:50 AM, Tzu-Li (Gordon) Tai <tzuli...@apache.org > > wrote: > >> The two blockers FLINK-6646 and FLINK-6714 have been merged. >> >> >> On 26 May 2017 at 1:45:55 AM, Robert Metzger (rmetz...@apache.org) wrote: >> >> Okay, it seems like there are two blockers for this RC. >> Once both PRs are merged, I'll create the next RC (ideally tomorrow) >> >> On Thu, May 25, 2017 at 11:10 AM, Tzu-Li (Gordon) Tai < >> tzuli...@apache.org> >> wrote: >> >> > I think https://issues.apache.org/jira/browse/FLINK-6714 is most >> likely a >> > blocker. >> > It basically makes most of our connectors that are not part of the >> binary >> > distribution and uses Java serialization for their operator state >> unusable >> > in standalone mode. >> > >> > There's a pending PR for the fix: https://github.com/ >> > apache/flink/pull/3987. >> > >> > Cheers, >> > Gordon >> > On 25 May 2017 at 12:45:12 AM, Till Rohrmann (trohrm...@apache.org) >> wrote: >> > >> > Forwarding my concern from the previous RC thread: >> > >> > https://issues.apache.org/jira/browse/FLINK-6646 might be a blocker, >> > because it voids Flink's HA capabilities. >> > >> > Robert argued that this is not a blocker because it was already broken >> in >> > 1.2 and users didn't complain about it. Therefore, it seems to affect >> only >> > corner cases. >> > >> > I think that partial high-availability is as good as no >> high-availability >> > at all. Therefore, I think we should cancel this RC and create a new one >> > containing a fix for the problem. Moreover, this is not only a problem >> of >> > the session mode but also for the per job cluster mode. Users simply >> didn't >> > run into the problem, because apparently their JM recovery didn't take >> > longer than 60s. >> > >> > Cheers, >> > Till >> > >> > >> > On Wed, May 24, 2017 at 6:25 PM, Robert Metzger <rmetz...@apache.org> >> > wrote: >> > >> > > Hi all, >> > > >> > > this is the first VOTEing release candidate for Flink 1.3.0 >> > > >> > > The commit to be voted on: >> > > e0a886e9 <http://git-wip-us.apache.org/repos/asf/flink/commit/e0a886e >> 9> >> > > (*http://git-wip-us.apache.org/repos/asf/flink/commit/e0a886e9 >> > > <http://git-wip-us.apache.org/repos/asf/flink/commit/e0a886e9>*) >> > > >> > > Branch: >> > > release-1.3.0-rc2 >> > > >> > > The release artifacts to be voted on can be found at: >> > > *http://people.apache.org/~rmetzger/flink-1.3.0-rc2/ >> > > <http://people.apache.org/~rmetzger/flink-1.3.0-rc2/>* >> > > >> > > The release artifacts are signed with the key with fingerprint >> D9839159: >> > > http://www.apache.org/dist/flink/KEYS >> > > >> > > The staging repository for this release can be found at: >> > > *https://repository.apache.org/content/repositories/orgapach >> eflink-1121 >> > > <https://repository.apache.org/content/repositories/orgapach >> eflink-1121 >> > >* >> > > >> > > ------------------------------------------------------------- >> > > >> > > >> > > The vote ends on Monday (May 29th), 7pm CET. >> > > >> > > [ ] +1 Release this package as Apache Flink 1.3.0 >> > > [ ] -1 Do not release this package, because ... >> > > >> > >> > >
