On Jun 21, 2018, at 12:38 PM, Kevin Risden <krisden@xxxxxxxxxx> wrote:
checked gpg, sha256, compiled and ran tests using JDK 8_172, 9.0.4, 10.0.1,
and 11-ea build 18.
I tried to build and run tests against Calcite with rc0. There will be some
changes required to Calcite due to CALCITE-2219. Looks like Calcite had
been assuming that "closed" connections could just be reused without doing
anything to them. It breaks some assumptions about pooling tests and others.
Some quick tests with Apache Solr and Avatica 0.12.0 rc0 look like there
are no problems for that integration.
On Thu, Jun 21, 2018 at 7:33 AM, Michael Mior <mmior@xxxxxxxxxxxx> wrote:
+1 (binding) checked hashes and compiled and ran tests
Le jeu. 21 juin 2018 à 08:21, Francis Chuang <francischuang@xxxxxxxxxx> a
I have created a build for Apache Calcite Avatica 1.12.0, release
Thanks to everyone who have contributed to this release.
You can read the release notes here:
The commit to be voted upon:
Its hash is 019a4ec4ac2c952f842bca7ecfcfc86761b0f9c6
The artifacts to be voted on are located here:
The hashes of the artifact are as follows:
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 Avatica 1.12.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 Avatica 1.11.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: