+1

        * API Compatibility Report: ok
        * Nightly CI: ok *
        * Signature: ok
        * Checksum : ok
        * Rat check (1.8.0_292): ok
         - mvn clean apache-rat:check -D skipTests
        * Rat check (11.0.11): ok
         - mvn clean apache-rat:check -D skipTests -D hadoop.profile=3.0
        * Built from source (1.8.0_292): ok
         - mvn clean install -D skipTests -DskipTests
        * Built from source (11.0.11): ok
         - mvn clean install -D skipTests -D hadoop.profile=3.0 -DskipTests

* There's a couple flakeys in the build history. They almost all fail with
timeout. TestSplitRegionWhileRSCrash, TestMergeTableRegionsWhileRSCrash,
TestLogRolling, TestFastFail, TestQuotaAdmin, TestUnknownServers,
TestAdminShell2

So far, we've had four commits land since the RC. Of this, I'm surprised
HBASE-27320 is filed as an "improvement" and not something like "Critical".
Perhaps we can have some further discussion on that ticket.

Thanks,
Nick

On Wed, Aug 24, 2022 at 11:52 AM Nick Dimiduk <[email protected]> wrote:

> Please vote on this Apache hbase release candidate,
> hbase-2.5.0RC1
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache hbase 2.5.0
> [ ] -1 Do not release this package because ...
>
> The tag to be voted on is 2.5.0RC1:
>
>   https://github.com/apache/hbase/tree/2.5.0RC1
>
> This tag currently points to git reference
>
>   2ecd8bd6d615ca49bfb329b3c0c126c80846d4ab
>
> 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.5.0RC1/
>
> Maven artifacts are available in a staging repository at:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1494/
>
> Artifacts were signed with the 0x18567F39 key which can be found in:
>
>   https://downloads.apache.org/hbase/KEYS
>
> To learn more about Apache hbase, please see
>
>   http://hbase.apache.org/
>
> Thanks,
> Your HBase Release Manager
>

Reply via email to