+1(binding)

I checked:
√ release files in the correct location
√ digital signature and hashes are 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
√ The maven artifacts look correct
√ Verified TPCDS correctness with data replication and worker kill

Thanks,
Ethan Feng

Fei Wang <feiw...@apache.org> 于2025年3月11日周二 07:40写道:
>
> +1,
> I checked
> - the git commit hash is correct
> - download links are valid
> - checksums are good
> - signatures are good
> - LICENSE and NOTICE look good.
> - Build from source is successful with command: build/make-distribution.sh 
> --sbt-enabled --release
> Regards,
> Fei Wang
>
> On 2025/03/10 06:59:07 Nicholas wrote:
> > Hi Celeborn community,
> >
> >
> > This is a call for a vote to release Apache Celeborn
> > 0.5.4-rc1
> >
> >
> > The git tag to be voted upon:
> > https://github.com/apache/celeborn/releases/tag/v0.5.4-rc1
> >
> >
> > The git commit hash:
> > cf6ac8cc1d0b013c21a4894776e560c3d63dc42e source and binary artifacts can be
> > found at:
> > https://dist.apache.org/repos/dist/dev/celeborn/v0.5.4-rc1
> >
> >
> > The staging repo:
> > https://repository.apache.org/content/repositories/orgapacheceleborn-1105
> >
> >
> > Fingerprint of the PGP key release artifacts are signed with:
> > 92B13217E2AD1470D58882EF7B41580856A83A36
> >
> >
> > 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