Thanks for sheparding this through Julian

On Mon, Dec 13, 2021, 11:52 AM Julian Hyde <[email protected]> wrote:

> Thanks to everyone who has tested the release candidate and given
> their comments and votes.
>
> A special thank you to all of you who worked over the weekend on this,
> fixing bugs, making release candidates, and reviewing and voting on
> the release candidates. The Log4j RCE issue has been a testing time
> for many Apache projects, and I am proud that we have risen to the
> challenge. I know that our users will be grateful that we take
> security issues seriously.
>
> The tally is as follows.
>
> 6 binding +1s:
> Francis
> Josh
> Jacques
> Julian
> Michael
> Stamatis
>
> 1 non-binding +1s:
> Alessandro
>
> No 0s or -1s.
>
> Therefore I am delighted to announce that the proposal to release
> Apache Calcite Avatica 1.20.0 has passed.
>
> Thanks everyone. We’ll now roll out the release. The announcement will
> follow shortly, but for those in a hurry to upgrade, I suspect that
> the artifacts will be on Maven Central in less than two hours from
> now.
>
> Julian
>
>
>
> On Dec 13, 2021, at 7:40 AM, Josh Elser <[email protected]> wrote:
>
> (sorry for the belated..) +1 (binding)
>
> * xsums/sigs are good
> * Can build from source
> * CALCITE-4395 a non-blocker, agreed
> * Git commit looks to be in order
>
> On 12/12/21 9:45 PM, Julian Hyde wrote:
>
> Hi all,
> Yesterday I started a vote for Apache Calcite Avatica 1.20.0, release
> candidate 0, and then canceled it due to CALCITE-4935. (See
> https://issues.apache.org/jira/browse/CALCITE-4935.) Note that the
> subject of this email ends "(release candidate 0) (second vote)".
> The artifacts are the same, but we have new information, namely the
> discussion about whether CALCITE-4935 is a show-stopper. My judgment,
> as release manager, that it is not a show-stopper, and therefore
> release candidate 0 is good. I have restarted the vote because I would
> like to give you all a chance to weigh in.
> This vote does NOT carry forward votes from the previous thread. If
> you voted yesterday, please vote again.
> The remainder of this email is the same as yesterday's email, except
> "The vote is open for the next 18 hours".
> You can read the release notes here:
>
> https://gitbox.apache.org/repos/asf/calcite-avatica-site-preview.git/avatica/docs/history.html
> The commit to be voted upon:
>
> https://gitbox.apache.org/repos/asf?p=calcite-avatica.git;a=commit;h=8f8377551e7b07dbc6119ecf196942bc99834452
> Its hash is 8f8377551e7b07dbc6119ecf196942bc99834452
> Tag:
>
> https://gitbox.apache.org/repos/asf?p=calcite-avatica.git;a=tag;h=refs/tags/avatica-1.20.0-rc0
> The artifacts to be voted on are located here:
>
> https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-1.20.0-rc0
> (revision 51334)
> The hashes of the artifacts are as follows:
>
> 2de57fb1823237ec2d73f2e26059b6a7f5f51ec8f6dcfdcb2eb0b562cf4ef141c4a0a8c430610815e85b0b1c1c60245062cbb075c6dc72a44a4f543a6813bff2
> *apache-calcite-avatica-1.20.0-src.tar.gz
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/content/repositories/orgapachecalcite-1122/org/apache/calcite/
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/jhyde.asc
> https://www.apache.org/dist/calcite/KEYS
> To create the jars and test Apache Calcite Avatica: "gradle build
> -Prelease -PskipSign".
> If you do not have a Java/Gradle environment available, you can run the
> tests
> using docker. To do so, install docker and docker-compose, then run
> "docker-compose run test" from the root of the directory.
> Please vote on releasing this package as Apache Calcite Avatica 1.20.0.
> The vote is open for the next 18 hours and passes if a majority of at
> least three +1 PMC votes are cast. (The voting period is shorter than
> usual.)
> [ ] +1 Release this package as Apache Calcite Avatica 1.20.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)
>

Reply via email to