+1 (binding) I checked - git commit hash is correct. - links are valid. -
"incubating" is in the name. - PGP keys are good. - hashes are correct. -
LICENSE looks good. - NOTICE looks good. - DISCLAIMER exists. - build
success from source code (macOS). ``` ./build/make-distribution.sh
--release ``` Thanks, Keyong Zhou

Zhongqiang Chen <zhongqiangc...@apache.org> 于2023年7月18日周二 18:34写道:

> Hi Celeborn community,
>
> This is a call for a vote to release Apache Celeborn (Incubating)
> 0.3.0-incubating-rc2
>
> The git tag to be voted upon:
>
> https://github.com/apache/incubator-celeborn/releases/tag/v0.3.0-incubating-rc2
>
> The git commit hash:
> 6c5e3f8e7021f409b44e6352142d13e7ac3ffe93The source and binary artifacts
> can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.3.0-incubating-rc2
>
> The staging repo:
> https://repository.apache.org/content/repositories/orgapacheceleborn-1036
>
> Fingerprint of the PGP key release artifacts are signed with:
> 4A99BC4356A17B2FCFDBF7EE220A9E2898A6A6D4
>
> My public key to verify signatures can be found in:
> https://dist.apache.org/repos/dist/release/incubator/celeborn/KEYS
>
> The vote will be open for at least 72 hours or until the necessary
> number of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and the reason)
>
> Checklist for release:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> Steps to validate the release:
> https://www.apache.org/info/verification.html
>
> * Download links, checksums and PGP signatures are valid.
> * Source code distributions have correct names matching the current
> release.
> * Release files have the word incubating in their name.
> * DISCLAIMER, LICENSE and NOTICE files are correct.
> * All files have license headers if necessary.
> * No unlicensed compiled archives bundled in source archive.
> * The source tarball matches the git tag.
> * Build from source is successful.
>
> Thanks,
> Zhongqiang Chen
>
>

Reply via email to