Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Fri, 26 May 2017 16:50:27 +0800
From: "Tzu-Li (Gordon) Tai" <tzulitai@apache.org>
To: dev@flink.apache.org
Message-ID: <etPan.5927ec53.f3892ed.371a@apache.org>
In-Reply-To: <CAGr9p8DAGd_p2fESdvsZVJOvZYkEh_Jm0yag6-SwgqoMfWkYZA@mail.gmail.com>
References: <CAGr9p8B2ZgTXq1+ybjsH8rFYzK4J2EvYdpVHddU0xGMPBD+2Og@mail.gmail.com>
 <CAC27z=OEZsfe1wAingkeub65gza2y_B4bD_ikuVwNOp7jpx8+w@mail.gmail.com>
 <etPan.59269f7f.1c176821.371a@apache.org>
 <CAGr9p8DAGd_p2fESdvsZVJOvZYkEh_Jm0yag6-SwgqoMfWkYZA@mail.gmail.com>
Subject: Re: [VOTE] Release Apache Flink 1.3.0 (RC2)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5927ec53_66871126_371a"
archived-at: Fri, 26 May 2017 08:50:34 -0000

--5927ec53_66871126_371a
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

The two blockers FLINK-6646 and FLINK-6714 have been merged.


On 26 May 2017 at 1:45:55 AM, Robert Metzger (rmetzger@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 <tzulitai@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 (trohrmann@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 <rmetzger@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/e0a886e9> 
> > (*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/orgapacheflink-1121 
> > <https://repository.apache.org/content/repositories/orgapacheflink-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 ... 
> > 
> 

--5927ec53_66871126_371a--