+1 non-binding But I found a little problem: The bcprov is not present in `apache-shardingsphere-5.1.0-shardingsphere-proxy-bin/LICENSE`, and there is a typo that the `bvprov` should be `bcprov` in filename of `apache-shardingsphere-5.1.0-shardingsphere-proxy-bin/licenses/LICENSE-bvprov-jdk15on.txt`.
I've checked: [x] Download links are valid. [x] Checksums and PGP signatures are valid. [x] Source code distributions have correct names matching the current release. [x] LICENSE and NOTICE files are correct for each ShardingSphere repo. [x] All files have license headers if necessary. [x] No compiled archives bundled in source archive. ----------------------------------------------- Weijie Wu 吴伟杰 Apache ShardingSphere Committer GitHub@TeslaCN Haoran Meng <menghao...@apache.org> 于2021年12月31日周五 15:01写道： > Hello ShardingSphere Community, > > This is a call for vote to release Apache ShardingSphere version 5.1.0 > > Release notes: > https://github.com/apache/shardingsphere/blob/5.1.0/RELEASE-NOTES.md > > The release candidates: > https://dist.apache.org/repos/dist/dev/shardingsphere/5.1.0/ > > Maven 2 staging repository: > > https://repository.apache.org/content/repositories/orgapacheshardingsphere-1072/org/apache/shardingsphere/ > > Git tag for the release: > https://github.com/apache/shardingsphere/tree/5.1.0/ > > Release Commit ID: > > https://github.com/apache/shardingsphere/commit/4079ee8e45adba15f370ffa6c8e5075453c0444d > > Keys to verify the Release Candidate: > https://dist.apache.org/repos/dist/dev/shardingsphere/KEYS > > Look here for how to verify this release candidate: > https://shardingsphere.apache.org/community/en/contribute/release/ > > GPG user ID: > menghaoran > > 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 with the reason > > PMC vote is +1 binding, all others are +1 non-binding. > > Checklist for reference: > > [ ] Download links are valid. > > [ ] Checksums and PGP signatures are valid. > > [ ] Source code distributions have correct names matching the current > release. > > [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. > > [ ] All files have license headers if necessary. > > [ ] No compiled archives bundled in source archive. > > > > > -- > Best, > Haoran Meng > Apache ShardingSphere >
