With 3 binding +1 and one non-binding +1, the vote has passed. Thanks to everyone for testing. I’ll go ahead and publish the artifacts.
—Vaibhav On 4/6/17, 8:48 AM, "Sushanth Sowmyan" <khorg...@gmail.com> wrote: >+1 (binding) > >Verified md5 and asc >KEYS obtained from hive match (from >https://people.apache.org/keys/group/hive.asc) , and is publically >searchable and signed. >RAT test succeeds >Source and binary tarballs look good >Compiling works, some base unit tests succeed. >Testing local mode works. > >On Wed, Apr 5, 2017 at 11:16 PM, Thejas Nair <thejas.n...@gmail.com> >wrote: >> +1 (binding) >> - Verified signature and checksum >> - Build from source >> - Ran simple queries in local mode with binary tar.gz >> - Checked RELEASE_NOTES file. Traditionally this file has had the set of >> patches fixed in previous releases as well ( ie, each new release was >> adding entries to the top of the file). This time it has only the new >>patch >> release patches. The old approach helps to quickly verify if patch is in >> the release. I think it would be good to fix that in branch. I think it >>is >> OK for this release. >> - README.txt has old 1.2.1 version number in it. IMO, we should just >>remove >> the mention of version in that file. Not a release blocker. >> >> >> >> >> On Wed, Apr 5, 2017 at 3:52 PM, Sergio Pena <sergio.p...@cloudera.com> >> wrote: >> >>> +1 (no-binding) >>> >>> I unpacked the bin and src packages. >>> Verified gpg and md5 signatures. >>> Check license and release notes files. >>> Run a few queries from hive-cli. >>> >>> - Sergio >>> >>> On Tue, Apr 4, 2017 at 11:12 AM, Ashutosh Chauhan >>><hashut...@apache.org> >>> wrote: >>> >>> > Verified md5 of src and binary tar balls. >>> > Built from src. >>> > Ran some simple queries like join, group by. >>> > All looks good. >>> > >>> > +1 >>> > >>> > Thanks, >>> > Ashutosh >>> > >>> > On Mon, Apr 3, 2017 at 4:47 PM, Vaibhav Gumashta < >>> > vgumas...@hortonworks.com> >>> > wrote: >>> > >>> > > Thanks for pointing out Ashutosh. Link to my PGP key: >>> > > http://pgp.mit.edu/pks/lookup?search=gumashta&op=index. >>> > > >>> > > I think it will take a day or so for the KEYS file to be updated >>>(it is >>> > > auto generated), but if you want to test the release in the >>>meantime, >>> > > please use the above link to access the signing key. >>> > > >>> > > Thanks, >>> > > ‹Vaibhav >>> > > >>> > > On 4/3/17, 2:53 PM, "Ashutosh Chauhan" <hashut...@apache.org> >>>wrote: >>> > > >>> > > >Hi Vaibhav, >>> > > > >>> > > >Can't locate your key at any of standard location. Can you point >>>out >>> > which >>> > > >key you used to sign the release? >>> > > > >>> > > >Thanks, >>> > > >Ashutosh >>> > > > >>> > > >On Mon, Apr 3, 2017 at 12:51 AM, Vaibhav Gumashta >>> > > ><vgumas...@hortonworks.com >>> > > >> wrote: >>> > > >> Hi everyone, >>> > > >> >>> > > >> Apache Hive 1.2.2 Release Candidate 0 is available here: >>> > > >> >>> > > >> >>>https://dist.apache.org/repos/dist/dev/hive/apache-hive-1.2.2-rc0/ >>> > > >> >>> > > >> Maven artifacts are available here: >>> > > >> >>> > > >> https://repository.apache.org/content/repositories/ >>> > orgapachehive-1072/ >>> > > >> >>> > > >> Source tag for RC0 is at: >>> > > >> https://github.com/apache/hive/releases/tag/release-1.2.2-rc0 >>> > > >> >>> > > >> Voting will conclude in 72 hours. >>> > > >> >>> > > >> Hive PMC Members: Please test and vote. >>> > > >> >>> > > >> Thanks, >>> > > >> -Vaibhav >>> > > >> >>> > > >> >>> > > >>> > > >>> > >>> >
