+1(binding) I checked: √ release files in the correct location √ digital signature and hashes correct √ LICENSE and NOTICE files exist and are correct √ the contents of the release match the tag in VCS √ can build the release from the source √ maven artifacts look correct
Thanks, Ethan Feng Nicholas Jiang <[email protected]> 于2024年10月28日周一 12:31写道： > > Hi Celeborn community, > > This is a call for a vote to release Apache Celeborn > 0.5.2-rc2 > > The git tag to be voted upon: > https://github.com/apache/celeborn/releases/tag/v0.5.2-rc2 > > The git commit hash: > 6f1c1d34773e33f483dadd17bc7d42d0055de1d5 source and binary artifacts can be > found at: > https://dist.apache.org/repos/dist/dev/celeborn/v0.5.2-rc2 > > The staging repo: > https://repository.apache.org/content/repositories/orgapacheceleborn-1084 > > 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
