Hi Ethan, Thanks for feedback of incorrect maven artifacts. Sorry for the mistake that missed the Spark shade client in the Maven staging repo. I will start the vote thread of 0.5.2-rc4 as soon as possible.
Regards, Nicholas Jiang On 2024/11/14 12:04:49 Ethan Feng wrote: > -1 (binding) > > Thanks for your effort in driving the new Celeborn release but the > Maven artifacts are not correct. Some shade client jars are lost in > the Maven staging repo. > > Thanks, > Ethan Feng > > rexxiong <[email protected]> 于2024年11月14日周四 15:08写道： > > > > +1 (binding) > > I checked > > - Download links are valid. > > - git commit hash is correct > > - Checksums and signatures are valid. > > - Successfully built the binary from the source on MacOs (Java 8) with > > Command: build/make-distribution.sh --sbt-enabled --release > > > > > > Thanks, > > Jiashu Xiong > > > > Nicholas Jiang <[email protected]> 于2024年11月12日周二 11:48写道： > > > > > Hi Celeborn community, > > > > > > This is a call for a vote to release Apache Celeborn > > > 0.5.2-rc3 > > > > > > The git tag to be voted upon: > > > https://github.com/apache/celeborn/releases/tag/v0.5.2-rc3 > > > > > > The git commit hash: > > > 8ac06dfe61fc2776d65c5d05bf0d1bf3123cb3ab source and binary artifacts can > > > be > > > found at: > > > https://dist.apache.org/repos/dist/dev/celeborn/v0.5.2-rc3 > > > > > > The staging repo: > > > https://repository.apache.org/content/repositories/orgapacheceleborn-1086 > > > > > > 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 >
