+1
Verified 3 jar's sha512.
Did basic WebUI check.
Ran all unit tests, passed.


On Thu, Feb 7, 2019 at 4:03 AM 张铎(Duo Zhang) <[email protected]> wrote:

> The first release candidate for HBase 2.1.3 is available for download:
>
>   https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.3RC0
>
> Maven artifacts are also available in a staging repository at:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1253/
>
> 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.3RC0, which currently points to
> commit
>
>   169f2aea2a9f31831201d3add598e6d7fb23079b
>
> 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 ~55 bug and improvement fixes done since the 2.1.2. There is
> an imcompatible issue, 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.3RC0/compatibility_report_2.1.2vs2.1.3RC0.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.3RC0/CHANGES.md
>
> The RELEASENOTES.md are here:
>
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.1.3RC0/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