FLINK-18902 and FLINK-18646 have been merged into the release-1.10 branch.
>From my side you are good to go to create the next RC now.

Cheers,
Till

On Wed, Aug 12, 2020 at 7:03 PM Zhu Zhu <reed...@gmail.com> wrote:

> Thank you all for the efforts verifying the RC. And thanks @Till Rohrmann
> <trohrm...@apache.org> for the information of FLINK-18646 and FLINK-18902.
>
> The vote is hereby canceled. I will prepare the next RC after FLINK-18646
> and FLINK-18902 are properly resolved.
>
> Thanks,
> Zhu Zhu
>
> Till Rohrmann <trohrm...@apache.org> 于2020年8月12日周三 下午10:59写道:
>
>> I've opened a PR for FLINK-18902 [1].
>>
>> [1] https://github.com/apache/flink/pull/13131
>>
>> Cheers,
>> Till
>>
>> On Wed, Aug 12, 2020 at 3:02 PM Till Rohrmann <trohrm...@apache.org>
>> wrote:
>>
>> > Another problem occurred recently [1]. I think we need to fix this
>> problem
>> > before releasing Flink 1.10.2. I will work on it.
>> >
>> > [1] https://issues.apache.org/jira/browse/FLINK-18902
>> >
>> > Cheers,
>> > Till
>> >
>> > On Wed, Aug 12, 2020 at 2:35 PM Till Rohrmann <trohrm...@apache.org>
>> > wrote:
>> >
>> >> -1 (binding), see below for the explanation.
>> >>
>> >> - verified checksums and signatures
>> >> - verified that dependency changes are reflected in NOTICE/LICENSE
>> files
>> >> - built Flink with Scala 2.12 support from sources
>> >> - Started cluster and ran example jobs, no suspicious log output
>> >>
>> >> I noticed that Flink 1.10.2 contains FLINK-15758 [1]. There was a
>> problem
>> >> with this ticket which was fixed with FLINK-18646 [2] but which was not
>> >> back ported to Flink 1.10.2. @Andrey Zagrebin <azagre...@apache.org>
>> was
>> >> there a specific reason why we didn't do it? I think the Flink 1.10.2
>> >> release should either contain both fixes or none. Hence, I vote -1
>> >> (binding) for this release until this problem is resolved.
>> >>
>> >> [1] https://issues.apache.org/jira/browse/FLINK-15758
>> >> [2] https://issues.apache.org/jira/browse/FLINK-18646
>> >>
>> >> Cheers,
>> >> Till
>> >>
>> >> On Wed, Aug 12, 2020 at 2:11 PM Timo Walther <twal...@apache.org>
>> wrote:
>> >>
>> >>> +1 (binding)
>> >>>
>> >>> I went through the commit diff and changed files of this release.
>> Could
>> >>> not spot anything suspicious.
>> >>>
>> >>> Regards,
>> >>> Timo
>> >>>
>> >>> On 11.08.20 14:47, Zhu Zhu wrote:
>> >>> > Hi everyone,
>> >>> >
>> >>> > Please review and vote on the release candidate #1 for the version
>> >>> 1.10.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 are signed with the key with
>> >>> > fingerprint C63E230EFFF519A5BBF2C9AE6767487CD505859C [3],
>> >>> > * all artifacts to be deployed to the Maven Central Repository [4],
>> >>> > * source code tag "release-1.10.2-rc1" [5],
>> >>> > * website pull request listing the new release and adding
>> announcement
>> >>> blog
>> >>> > post [6].
>> >>> >
>> >>> > The vote will be open for at least 72 hours. It is adopted by
>> majority
>> >>> > approval, with at least 3 PMC affirmative votes.
>> >>> >
>> >>> > Thanks,
>> >>> > Zhu Zhu
>> >>> >
>> >>> > [1]
>> >>> >
>> >>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12347791
>> >>> > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.10.2-rc1/
>> >>> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
>> >>> > [4]
>> >>>
>> https://repository.apache.org/content/repositories/orgapacheflink-1383/
>> >>> > [5]
>> >>> >
>> >>>
>> https://github.com/apache/flink/commit/4033014695061b05a720edc766f1c722cdb32d6e
>> >>> > [6] https://github.com/apache/flink-web/pull/366
>> >>> >
>> >>>
>> >>>
>>
>

Reply via email to