Verified signatures/hashes and compiled and ran tests. Also ran some of the
integration tests. Unfortunately the VM doesn't seem to build properly at
the moment, but that's a separate issue.
As for the signature not being in the web of trust, perhaps we could have a
virtual key signing party at some point?
2016-09-17 7:49 GMT-04:00 Jesus Camachorodriguez <jcama...@apache.org>:
> Hi all,
> I have created a build for Apache Calcite 1.9.0, release candidate 1.
> Thanks to everyone who has contributed to this release.
> You can read the release notes here:
> The commit to be voted upon:
> Its hash is 08c56b158ffcfcf205a919cc9fff77a692e649f6.
> The artifacts to be voted on are located here:
> The hashes of the artifacts are as follows:
> src.tar.gz.md5 b3b6a15671b1e8ffd7f989398e050de4
> src.tar.gz.sha1 8f17b2d7896bac6123ae4a1491e04f4960094a59
> src.zip.md5 7c66353701d1924a9e2656bd76e570cb
> src.zip.sha1 8a5c7d27b0240cbcacd565eadf451de9dff6d2fa
> A staged Maven repository is available for review at:
> Release artifacts are signed with the following key:
> Please vote on releasing this package as Apache Calcite 1.9.0.
> The vote is open for the next 96 hours and passes if a majority of
> at least three +1 PMC votes are cast.
> [ ] +1 Release this package as Apache Calcite 1.9.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)