+1(non-binding)

I checked the following items:
1. git commit hash
2. existence of LICENSE and NOTICE files
3. build from source code
4. validity of staging repo link

Thanks,
Xu Huang

Nicholas Jiang <[email protected]> 于2024年11月22日周五 21:51写道:

> Hi Celeborn community,
>
> This is a call for a vote to release Apache Celeborn
> 0.5.2-rc6
>
> The git tag to be voted upon:
> https://github.com/apache/celeborn/releases/tag/v0.5.2-rc6
>
> The git commit hash:
> 513bd5995df3f062ea0e8edea12c02690bd2393a source and binary artifacts can be
> found at:
> https://dist.apache.org/repos/dist/dev/celeborn/v0.5.2-rc6
>
> The staging repo:
> https://repository.apache.org/content/repositories/orgapacheceleborn-1091
>
> Fingerprint of the PGP key release artifacts are signed with:
> 9EC4BC38E04BC086C026AC681FC79E01BA3B84D5
>
> My public key to verify signatures can be found in:
> https://dist.apache.org/repos/dist/release/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)
>
> 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.
> * 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.
>
> Regards,
> Nicholas Jiang

Reply via email to