Hi Attila, Thanks a lot for working on the 2.3.0 release! Found some problems:
- The link https://github.com/apache/ratis/tree/ratis-2.3.0-rc0 points to the commit id a37571aca4ed4bae8f3aebe696c806a2d54511ea but not 87c54d0dbb256434e9829307017e945a28bef887. - There is a warning "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository." The commit a37571a seems not yet pushed to Apache. We usually push the rc to a branch named with the version, i.e. 2.3.0 in this case. I think we need to roll rc1. Regards, Tsz-Wo On Thu, May 12, 2022 at 12:24 AM Attila Doroszlai <[email protected]> wrote: > Hi all, > > Based on previous discussion, I am calling a vote for Apache Ratis > Release 2.3.0 rc0. > > The git tag to be voted upon: > https://github.com/apache/ratis/tree/ratis-2.3.0-rc0 > > The git commit hash: > 87c54d0dbb256434e9829307017e945a28bef887 > > The source and binary tarballs can be found at: > https://dist.apache.org/repos/dist/dev/ratis/2.3.0/rc0 > > Fingerprint of the PGP key release artifacts are signed with: > 0949 35E7 9D62 A9C4 A969 CCE2 B629 7DE9 82CF 1F4E > > My public key to verify signatures can be found in: > https://dist.apache.org/repos/dist/dev/ratis/KEYS > > Maven artifacts are staged at: > https://repository.apache.org/content/repositories/orgapacheratis-1065/ > > This vote will remain open for 7 days. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Starting with my +1 (binding): > > * Verified checksum, signature, git hash > * Compared source tarball to repo at the given tag > * Ran Rat check on source > * Ran regular Ozone CI using the staged jars [1] > (failure in dependency check is my fault, not a Ratis release problem) > > Please vote on releasing this RC. Thank you in advance. > > -Attila > > [1] https://github.com/adoroszlai/hadoop-ozone/actions/runs/2307571187 >
