I'm +1. Checked signature and checksum, verified binaries, compiled, ran some
tests and queries - didn't find any issues.
The concern seems to be that we don't release often enough - rebasing the
branch and re-stabilizing would just delay having a release further. We can
always put a new one together, rather than scrapping this one.
Thanks,
Gunther.
________________________________________
From: Eugene Koifman <ekoif...@hortonworks.com>
Sent: Friday, July 14, 2017 10:18 AM
To: dev@hive.apache.org
Subject: Re: [VOTE] Apache Hive 2.3.0 Release Candidate 1
Another issue is that the branch for 2.3 was cut 2 or 3 month ago. Given how
infrequently releases are made, would it not make more sense to recut it at
this point?
On 7/14/17, 8:20 AM, "Sergio Pena" <sergio.p...@cloudera.com> wrote:
What happened with the 2.2.0 release? is it confusing to jump from 2.1 ->
2.3 without having a 2.2 release previously?
On Fri, Jul 14, 2017 at 2:02 AM, Pengcheng Xiong <pxi...@apache.org> wrote:
> Apache Hive 2.3.0 Release Candidate 1 is available here:
>
> Artifacts:
> tag: *https://github.com/apache/hive/releases/tag/release-2.3.0-rc1
> <https://github.com/apache/hive/releases/tag/release-2.3.0-rc1>*
> tar ball: http://home.apache.org/~pxiong/apache-hive-2.3.0
> <http://home.apache.org/~pxiong/hive-storage-2.4.0/>
>
> Voting will conclude in 72 hours.
>
> Hive PMC Members: Please test and vote.
>
> Here is my +1 after running rat check, md5 check and simple queries.
>
> Thanks.
>
> Best
> Pengcheng
>
