Also with my own +1. I have deployed the version on a medium cluster (80+ nodes) for 3 days, it runs well so far.
Thanks, Cheng Pan > On Dec 5, 2024, at 15:26, Keyong Zhou <[email protected]> wrote: > > +1 (binding) > > I checked > - git commit hash is correct. > - links are valid. > - signatures are good. > ``` > gpg --import KEYS > gpg --verify apache-celeborn-0.4.3-bin.tgz.asc > gpg --verify apache-celeborn-0.4.3-source.tgz.asc > ``` > - checksums are good. > ``` > shasum --check apache-celeborn-0.4.3-source.tgz.sha512 > shasum --check apache-celeborn-0.4.3-bin.tgz.sha512 > ``` > - LICENSE looks good. > - NOTICE looks good. > - build success from source code (macOS). > ``` > ./build/make-distribution.sh --sbt-enabled --release > ``` > > Regards, > Keyong Zhou > > Cheng Pan <[email protected]> 于2024年12月3日周二 17:06写道： > >> Hi Celeborn community, >> >> This is a call for a vote to release Apache Celeborn 0.4.3-rc0 >> >> The git tag to be voted upon: >> https://github.com/apache/celeborn/releases/tag/v0.4.3-rc0 >> >> The git commit hash: >> 52cb34603c10bddddfe2bcff0feacc4e5f8d1990 >> >> source and binary artifacts can be found at: >> https://dist.apache.org/repos/dist/dev/celeborn/v0.4.3-rc0 >> >> The staging repo: >> https://repository.apache.org/content/repositories/orgapacheceleborn-1092 >> >> Fingerprint of the PGP key release artifacts are signed with: >> 8FC8075E1FDC303276C676EE8001952629BCC75D >> >> 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. >> >> Thanks, >> Cheng Pan >> >>
