+1

       * Signature: ok
        * Checksum : ok
        * Rat check (1.8.0_191): ok
         - mvn clean apache-rat:check
        * Built from source (1.8.0_191): ok
         - mvn clean install -DskipTests
        * Unit tests pass (1.8.0_191): failed
         - mvn package -P runSmallTests

The test failed because I had my vpn up which clashes w/ the kerberos test.

Changes and release notes look good (did not verify changes matches issues
in git).
API compat looks good.
Started up standalone with binary built from src. Loaded and verified data
made it. Exercised shell. Looked at UI.

S

On Thu, May 20, 2021 at 12:11 PM Andrew Purtell <apurt...@apache.org> wrote:

> Please vote on this Apache HBase release candidate, hbase-2.4.3RC1.
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache HBase 2.4.3
> [ ] -1 Do not release this package because ...
>
> The tag to be voted on is 2.4.3RC1:
>
>     https://github.com/apache/hbase/tree/2.4.3RC1
>
> The release files, including signatures, digests, as well as CHANGES.md
> and RELEASENOTES.md included in this RC can be found at:
>
>     https://dist.apache.org/repos/dist/dev/hbase/2.4.3RC1/
>
> These sources correspond with the git tag "2.4.3RC1" (401b60b217).
>
> Temporary Maven artifacts are available in the staging repository:
>
>
> https://repository.apache.org/content/repositories/orgapachehbase-1447/
>
> Artifacts were signed with the apurt...@apache.org key which can be found
> in:
>
>     https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> The API compatibility report for this RC can be found at:
>
>
>
> https://dist.apache.org/repos/dist/dev/hbase/2.4.3RC1/api_compare_2.4.2_to_2.4.3RC1.html
>
> We performed the following successful pre-flight checks before
> announcing the previous RC, RC0:
>
>     - Unit tests
>
>     - 10 TB Common Crawl data load via IntegrationTestLoadCommonCrawl,
>       slowDeterministic policy
>
> To learn more about Apache HBase, please see
>
>     http://hbase.apache.org/
>
> Thanks,
> Your HBase Release Manager
>

Reply via email to