+1 based on the following:

verified signatures
ran unit test suite - pass
loaded onto a small cluster and performed sanity checks (hbase shell, UI,
etc)

Cheers

On Wed, Aug 26, 2015 at 9:16 PM, Nick Dimiduk <ndimi...@apache.org> wrote:

> Hello again devs,
>
> This "third time's the charm" edition release candidate of HBase 1.1.2
> (HBase-1.1.2RC2) is available for download at
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.2RC2/
>
> Maven artifacts are also available in the staging repository
> https://repository.apache.org/content/repositories/orgapachehbase-1115/
>
> Artifacts are signed with my code signing subkey 0xAD9039071C3489BD,
> available in the Apache keys directory
> https://people.apache.org/keys/committer/ndimiduk.asc and in our project
> KEYS files at https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> There's a signed tag for this release at
>
> https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=tag;h=b54078ddc30b9feb09aa36f3cf9fa8af757fa77b
>
> The detailed source and binary compatibility report vs 1.1.0 has been
> published for your review, at
> http://people.apache.org/~ndimiduk/1.1.0_1.1.2RC2_compat_report.html
>
> HBase 1.1.2 is the second patch release in the HBase 1.1 line, continuing
> on the theme of bringing a stable, reliable database to the Hadoop and
> NoSQL communities. This release includes over 80 bug fixes since the 1.1.1
> release. Notable correctness fixes include HBASE-14054, HBASE-12865,
> HBASE-13993, HBASE-13337, HBASE-14013, HBASE-13895.
>
> This release candidate is identical to the RC1 tag. The only difference is
> it was built with the updated make_rc.sh script attached to HBASE-14318.
>
> The full list of fixes included in this release is available at
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12332793
> and in the CHANGES.txt file included in the distribution.
>
> Please try out this candidate and vote +/-1 by Monday, 2015-08-31 23:59
> UTC-07:00 as to whether we should release these artifacts as HBase 1.1.2.
>
> Thanks,
> Nick
>

Reply via email to