+1 binding.

My check list,


[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.


 Juan Pan (Trista)
                         
Senior DBA & PMC of Apache ShardingSphere
E-mail: [email protected]




On 08/11/2020 16:32,[email protected]<[email protected]> wrote:
Hello ShardingSphere Community,

This is a call for vote to release Apache ShardingSphere ElasticJob UI
version 3.0.0-alpha

Release notes:
https://github.com/apache/shardingsphere-elasticjob-ui/blob/master/RELEASE-NOTES.md

The release candidates:
https://dist.apache.org/repos/dist/dev/shardingsphere/elasticjob-ui-3.0.0-alpha/

Git tag for the release:
https://github.com/apache/shardingsphere-elasticjob-ui/tree/shardingsphere-elasticjob-ui-3.0.0-alpha/

Release Commit ID:
https://github.com/apache/shardingsphere-elasticjob-ui/commit/174661dc77366eb8ab0742ac61ab0f5c84a60f2c

Keys to verify the Release Candidate:
https://dist.apache.org/repos/dist/dev/shardingsphere/KEYS

Look at here for how to verify this release candidate:
https://shardingsphere.apache.org/community/en/contribute/release-elasticjob-ui/

GPG user ID:
zhangliang

The vote will be open for at least 72 hours or until 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 is +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.


------------------

Sincerely,
Liang Zhang (John)
Apache ShardingSphere

Reply via email to