Hi,

I think FLINK-7352 is only a testing instability. We should definitely fix that 
but I don't think it should block the release, which has quite a few critical 
fixes.

Best,
Aljoscha

> On 5. Aug 2017, at 00:05, Ted Yu <yuzhih...@gmail.com> wrote:
> 
> When I ran integration tests, I bumped into:
> FLINK-7352
> 
> Should this be resolved for 1.3.2 ?
> 
> Thanks
> 
> On Sun, Jul 30, 2017 at 12:07 AM, Aljoscha Krettek <aljos...@apache.org>
> wrote:
> 
>> Hi everyone,
>> 
>> Please review and vote on the release candidate #2 for the version 1.3.2,
>> as follows:
>> [ ] +1, Approve the release
>> [ ] -1, Do not approve the release (please provide specific comments)
>> 
>> 
>> The complete staging area is available for your review, which includes:
>> * JIRA release notes [1],
>> * the official Apache source release and binary convenience releases to be
>> deployed to dist.apache.org [2], which is signed with the key with
>> fingerprint 0xA8F4FD97121D7293 [3],
>> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag "release-1.3.2-rc2" [5],
>> * website pull request listing the new release and adding announcement
>> blog post [6].
>> 
>> The vote will be open for at least 72 hours (excluding this current
>> weekend). It is adopted by majority approval, with at least 3 PMC
>> affirmative votes.
>> 
>> Please use the provided document, as discussed before, for coordinating
>> the testing efforts: [7]
>> 
>> Thanks,
>> Aljoscha
>> 
>> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12315522&version=12340984
>> [2] http://people.apache.org/~aljoscha/flink-1.3.2-rc2/
>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
>> [4] https://repository.apache.org/content/repositories/
>> orgapacheflink-1133/
>> [5] https://git-wip-us.apache.org/repos/asf?p=flink.git;a=tag;h=
>> e38825d0c8e7fe2191a4c657984d9939ed8dd0ad
>> [6] https://github.com/apache/flink-web/pull/75
>> [7] https://docs.google.com/document/d/1dN9AM9FUPizIu4hTKAXJSbbAORRdr
>> ce-BqQ8AUHlOqE/edit?usp=sharing

Reply via email to