+1, I checked - the git commit hash is correct - download links are valid - checksums are good ``` shasum --check apache-celeborn-0.5.3-bin.tgz.sha512 shasum --check apache-celeborn-0.5.3-source.tgz.sha512 ``` - signatures are good ``` gpg --verify apache-celeborn-0.5.3-bin.tgz.asc apache-celeborn-0.5.3-bin.tgz gpg --verify apache-celeborn-0.5.3-source.tgz.asc apache-celeborn-0.5.3-source.tgz ``` - LICENSE and NOTICE look good. - Build from source is successful. ``` ./build/make-distribution.sh --release ``` Regards, Fei Wang
On 2025/01/03 20:30:04 Mridul Muralidharan wrote: > +1 > > Signatures, digests, etc check out fine. > Checked out tag and build/tested with -Pspark-3.1 -Pjdk-11 > > Regards, > Mridul > > > On Fri, Jan 3, 2025 at 1:39 AM Ethan Feng <ethanf...@apache.org> wrote: > > > Hi, Celeborn community, > > > > This is a call for a vote to release Apache Celeborn > > 0.5.3-rc2 > > > > The git tag to be voted upon: > > https://github.com/apache/celeborn/releases/tag/v0.5.3-rc2 > > > > The git commit hash: > > db8267542d4ae72182097862a027d6b5256dd1f2 > > > > Source and binary artifacts can be found at: > > https://dist.apache.org/repos/dist/dev/celeborn/v0.5.3-rc2 > > > > The staging repo: > > https://repository.apache.org/content/repositories/orgapacheceleborn-1096 > > > > The fingerprint of the PGP key release artifacts is signed with the > > following: > > FCF2 0BB2 9C7B EFDF 58F9 98F7 6392 F71F 3735 6FA0 > > > > 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 the source archive. > > * The source tarball matches the git tag. > > * Build from source is successful. > > > > The following scenarios were tested: > > 1. TPC-DS with data replication on, random worker kill, verified data > > correctness. > > 2. TPC-DS with random worker kill, verified data correctness. > > 3. TPC-DS with stage rerun, verified data correctness. > > > > Regards, > > Ethan Feng > > >
