Sure. Would you please merge it to release-2.15.0, and I'll rebuild
artifacts and share the RC2?

On Wed, Aug 14, 2019 at 1:53 PM Chamikara Jayalath <[email protected]>
wrote:

> Can we rebuild to include the fix for
> https://issues.apache.org/jira/browse/BEAM-7866 which was merged
> yesterday ? (looks like fix version was changed to 2.16.0)
>
> Thanks,
> Cham
>
> On Wed, Aug 14, 2019 at 1:42 PM Yifan Zou <[email protected]> wrote:
>
>> Hi everyone,
>> Please review and vote on the release candidate #1 for the version
>> 2.15.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
>> AC9DB4F14CC90F37080F2C5B6D18F9A7F8DA25E1 [3].
>> * All artifacts to be deployed to the Maven Central Repository [4].
>> * Source code tag "v2.15.0-RC1" [5].
>> * Website pull request listing the release [6], 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.15.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,
>> Yifan Zou
>>
>> [1]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12345489
>> [2] https://dist.apache.org/repos/dist/dev/beam/2.15.0/
>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1081/
>> [5] https://github.com/apache/beam/tree/v2.15.0-RC1
>> [6] https://github.com/apache/beam/pull/9341
>> [7] https://github.com/apache/beam-site/pull/592
>> [8]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit?pli=1#gid=1036192804
>>
>

Reply via email to