Thanks for finding this Ahmet. Please consider the vote for RC2 canceled.

Andrew

On Tue, Apr 9, 2019 at 9:25 AM Ahmet Altay <al...@google.com> wrote:

> -1 unfortunately.
>
> Reason is https://issues.apache.org/jira/browse/BEAM-7038. 2.12 includes
> changes to coders that are not compatible with previous versions breaking
> some Dataflow use cases.
>
> On Mon, Apr 8, 2019 at 3:54 PM Andrew Pilloud <apill...@google.com> wrote:
>
>> Hi everyone,
>>
>> Please review and vote on the release candidate #2 for the version
>> 2.12.0, 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 to be deployed to dist.apache.org [2],
>> which is signed with the key with fingerprint
>> 9E7CEC0661EFD610B632C610AE8FE17F9F8AE3D4 [3],
>> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag "v2.12.0-RC2" [5],
>> * website pull request listing the release [6] and publishing the API
>> reference manual [7].
>> * Python artifacts are deployed along with the source release to the
>> dist.apache.org [2].
>> * Validation sheet with a tab for 2.12.0 release to help with validation
>> [8].
>>
>> The vote will be open for at least 72 hours. It is adopted by majority
>> approval, with at least 3 PMC affirmative votes.
>>
>> Thanks,
>> Andrew
>>
>> [1]
>> https://jira.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12344944
>> [2] https://dist.apache.org/repos/dist/dev/beam/2.12.0/
>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1066/
>> [5] https://github.com/apache/beam/tree/v2.12.0-RC2
>> [6] https://github.com/apache/beam/pull/8215
>> [7] https://github.com/apache/beam-site/pull/588
>> [8]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=1007316984
>>
>

Reply via email to