With 3 binding +1s and 2 non-binding +1s, the vote passes. Will push 2.1.3
out soon.

And thanks Stephen, the tool is great. But we still need 3 PMCs to vote +1
if we want to make a release, this is required by the ASF policy, an
automatic tool can not be counted as a binding vote...

Anyway, it will take less time for PMCs to vote on a release if we have a
good tool for verifying a release, which means we will likely to have more
PMCs to vote, so thanks for your sharing:)

张铎(Duo Zhang) <palomino...@gmail.com> 于2019年2月14日周四 上午8:48写道:

> +1(binding)
>
> The RC is generated by me so most things such as rat check, signature,
> etc, are all fine.
>
> Run UTs with openjdk 8u202: all passed
> Run ITBLL with deterministic, 3 loops, 1B rows per each loop: passed.
>
> Tak-Lon (Stephen) Wu <taklo...@gmail.com> 于2019年2月14日周四 上午2:15写道:
>
>> +1 (non-bindling)
>>
>>    - checked sums and signatures: ok
>>    - Rat check (8u192):  ok
>>       - mvn apache-rat:check
>>    - built from source: ok (8u192)
>>       - mvn clean install -DskipTests
>>    - Unit tests pass: ok (8u92)
>>       - mvn test -P runAllTests
>>
>>
>> I have been using this script
>> <https://drive.google.com/open?id=1iwIp3sj4Ssb6KWyHIr94CyDLLo8rVnn8>,
>> e.g. bash
>> hbase-vote.sh 2.1.3 hbase-2.1.3RC1
>> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.3RC1 to confirm
>> above, hopefully this will be handy for others.
>>
>> And I'm assuming the community has an automation running for these
>> checking
>> in somewhere, if not, IMO should we introduce an automation and simplify
>> few steps of checking the new release candidate?
>>
>> -Stephen
>>
>> On Wed, Feb 13, 2019 at 9:21 AM Norbert Kalmar
>> <nkal...@cloudera.com.invalid>
>> wrote:
>>
>> > +1 (non-binding)
>> >
>> > Checksums: ok
>> > Build from source: ok
>> > Unit tests: ok
>> > Start hbase in standalone: ok
>> > Basic shell commands: ok
>> >
>> > On Tue, Feb 12, 2019 at 5:49 PM Peter Somogyi <psomo...@apache.org>
>> wrote:
>> >
>> > > +1 (binding)
>> > >
>> > > Checked signatures, checksums: ok
>> > > Apache Rat check: ok
>> > > Build source: ok (jdk1.8.0_201)
>> > > Unit tests: ok
>> > > LTT 1M rows: ok
>> > > Run in pseudo distributed mode: ok (Hadoop 2.7.7)
>> > > Shell basic commands: ok
>> > > Web UI: ok
>> > > Tested RS Group: ok
>> > >
>> > > On Tue, Feb 12, 2019 at 7:48 AM Guanghao Zhang <zghao...@gmail.com>
>> > wrote:
>> > >
>> > > > +1 (binding)
>> > > >
>> > > > hbase-2.1.3-bin.tar.gz (jdk1.8.0_171)
>> > > > - Verified sha512: ok
>> > > > - Start HBase in standalone mode: ok
>> > > > - Verified with shell,
>> create/disable/enable/drop/get/put/scan/delete:
>> > ok
>> > > > - Checked master/regionserver/region Web UI: ok
>> > > > - PE write/read 100K rows: good
>> > > >
>> > > > hbase-2.1.3-src.tar.gz (jdk1.8.0_171)
>> > > > - Verified sha512: ok
>> > > > - Build tarball: ok
>> > > > - Start HBase in standalone mode: ok
>> > > > - Verified with shell,
>> create/disable/enable/drop/get/put/scan/delete:
>> > ok
>> > > > - Checked master/regionserver/region Web UI: ok
>> > > > - PE write/read 100K rows: good
>> > > >
>> > > > 张铎(Duo Zhang) <palomino...@gmail.com> 于2019年2月11日周一 下午8:15写道:
>> > > >
>> > > > > The second release candidate for HBase 2.1.3 is available for
>> > download:
>> > > > >
>> > > > >   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.3RC1
>> > > > >
>> > > > > Maven artifacts are also available in a staging repository at:
>> > > > >
>> > > > >
>> > > >
>> > https://repository.apache.org/content/repositories/orgapachehbase-1254/
>> > > > >
>> > > > > Artifacts are signed with my key (9AD2AE49) published in our KEYS
>> > file
>> > > at
>> > > > >
>> > > > >  http://www.apache.org/dist/hbase/KEYS
>> > > > >
>> > > > > The RC corresponds to the signed tag 2.1.3RC1, which currently
>> points
>> > > to
>> > > > > commit
>> > > > >
>> > > > >   da5ec9e4c06c537213883cca8f3cc9a7c19daf67
>> > > > >
>> > > > > HBase 2.1.3 is the fourth maintenance release in the HBase 2.1
>> line,
>> > > > > continuing on the theme of bringing a stable, reliable database to
>> > the
>> > > > > Hadoop and NoSQL communities. It fixes CVE-2018-1320 by upgrading
>> > > thrift
>> > > > > dependency from 0.9.3 to 0.12.0, all hbase users who use thrift
>> are
>> > > > highly
>> > > > > recommended to upgrade.
>> > > > >
>> > > > > 2.1.3 includes ~60 bug and improvement fixes done since the 2.1.2.
>> > > There
>> > > > is
>> > > > > an incompatible change, HBASE-21684, where we change the
>> superclass
>> > of
>> > > > > StoppedRpcClientException from HBaseIOException to
>> > > DoNotRetryIOException,
>> > > > > should be low risk, and feel free to contact us if this breaks
>> > anything
>> > > > for
>> > > > > you.
>> > > > >
>> > > > > The detailed source and binary compatibility report vs 2.1.2 has
>> been
>> > > > > published for your review, at:
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.3RC1/compatibility_report_2.1.2vs2.1.3RC1.html
>> > > > >
>> > > > > The report shows no incompatibilities.
>> > > > >
>> > > > > The full list of fixes included in this release is available in
>> the
>> > > > > CHANGES.md that ships as part of the release also available here:
>> > > > >
>> > > > >
>> > >
>> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.3RC1/CHANGES.md
>> > > > >
>> > > > > The RELEASENOTES.md are here:
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.3RC1/RELEASENOTES.md
>> > > > >
>> > > > > Please try out this candidate and vote +1/-1 on whether we should
>> > > release
>> > > > > these artifacts as HBase 2.1.3.
>> > > > >
>> > > > > The VOTE will remain open for at least 72 hours.
>> > > > >
>> > > > > Thanks
>> > > > >
>> > > >
>> > >
>> >
>>
>

Reply via email to