+1

* Signature: ok
* Checksum : ok
* Rat check (1.8.0_171): ok
 - mvn clean apache-rat:check
* Built from source (1.8.0_171): ok
 - mvn clean install  -DskipTests
* Unit tests pass (1.8.0_171): ok
 - mvn package -P runSmallTests  -Dsurefire.rerunFailingTestsCount=3

Flaky-tests build seems to be getting aborted consistently [1]. Do we need
to spend more time here or we can ignore it as this is perhaps the last
patch release in 2.2 release line?
+1 vote remains if we can safely ignore this for now. Our stable pointers
are already moved to 2.3, hence I am fine with this.

1.
https://ci-hadoop.apache.org/job/HBase/job/HBase-Flaky-Tests/job/branch-2.2/


On Sun, Apr 11, 2021 at 6:04 PM Guanghao Zhang <zghao...@gmail.com> wrote:

> Please vote on this release candidate (RC) for Apache HBase 2.2.7.
> Meanwhile, as branch-2.2 will be EOL, please don't push new commits to it.
> And this will be the last one of the 2.2.x releases. Thanks.
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache HBase 2.2.7
> [ ] -1 Do not release this package because ...
>
> The tag to be voted on is 2.2.7RC0. The release files, including
> signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/
>
> Maven artifacts are available in a staging repository at:
> https://repository.apache.org/content/repositories/orgapachehbase-1440/
>
> Signatures used for HBase RCs can be found in this file:
> https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> The list of bug fixes going into 2.2.7 can be found in included
> CHANGES.md and RELEASENOTES.md available here:
> https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/CHANGES.md
> https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/RELEASENOTES.md
>
> A detailed source and binary compatibility report for this release is
> available at:
>
> https://dist.apache.org/repos/dist/dev/hbase/2.2.7RC0/api_compare_2.2.7RC0_to_2.2.6.html
>
> To learn more about Apache HBase, please see http://hbase.apache.org/
>
> Thanks,
> Guanghao Zhang
>

Reply via email to