Following https://issues.apache.org/jira/browse/CALCITE-1972 <https://issues.apache.org/jira/browse/CALCITE-1972> I thought we were only going to generate .sha256, not .md5 anymore. (I did this for avatica-1.11 recently, apparently not for calcite1-15 when I was RM.)
> On Mar 14, 2018, at 1:14 AM, Jesus Camacho Rodriguez <jcama...@apache.org> > wrote: > > Hi all, > > I have created a build for Apache Calcite 1.16.0, release candidate 0. > > Thanks to everyone who has contributed to this release. > You can read the release notes here: > https://github.com/apache/calcite/blob/branch-1.16/site/_docs/history.md > > The commit to be voted upon: > http://git-wip-us.apache.org/repos/asf/calcite/commit/96b73060fdc77db9c13e40f6f82f374bb41d12c8 > > Its hash is 96b73060fdc77db9c13e40f6f82f374bb41d12c8. > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.16.0-rc0 > > The hashes of the artifacts are as follows: > src.tar.gz.md5 4849ebf6a1968111aca7c86ace193a9c > src.tar.gz.sha256 > 92d8c18cdcda81e81ddbd53bab92acdd53b021bc0d452a0b8c21f51ecb1dfcdf > src.zip.md5 0da85ae5de97a0b5d989c140e5d41044 > src.zip.sha256 > d096286a00f2cee588485f4bcb9d051eaff4ed2e4874084464ec76eea257a79e > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachecalcite-1042 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/jcamacho.asc > > Please vote on releasing this package as Apache Calcite 1.16.0. > > The vote is open for the next 72 hours and passes if a majority of > at least three +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Calcite 1.16.0 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > > Here is my vote: > > +1 (binding) > > Jesús > > >
