>1. I did checked every tar/zip checksums before/after the release, would write id down in the mail next time ~
Ok, it looks like I did not express it properly. Danny>The artifacts to be voted on are located here: Danny> https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.22.0-rc2/ The vote mail says nothing about apache-calcite-1.22.0-src.zip, so it means that the release archives are invalid, so it means there's -1 until the list of staged artifacts is sorted out. It is important that "vote mail" sets the full expectation on the set of released files. Now there's a mismatch between the list of staged files and the list of files in the vote. >3. I did try the auto tag task from the Gradle prepareVote, but it fails every time and reports the authentication problem when creating the tag What is the error message? AFAIK it should not require credentials to create the tag, however, it needs authentication to push the tag to the Git server. > what’s the difference then ? It is still a tag The difference is in the name. Autogenerated tags would be like v1.22-rc2 which has a clear tint of being a release candidate. >4. Would represent the diff in the mail between different RCs Having different tags for different RC enables the following: https://github.com/apache/calcite-avatica/compare/avatica-1.16.0-rc0..avatica-1.16.0-rc1 Vladimir
