+1 (non-binding) I checked: * Signature: OK * Checksum : OK * Rat check (1.8.0_421 and 17.0.12): OK - mvn clean apache-rat:check * Build from source (1.8.0_421 and 17.0.12): OK - mvn clean install -DskipTests -t toolchains.xml * Unit Tests (1.8.0_421 and 17.0.12): OK - mvn clean package -P release -Dsurefire.rerunFailingTestsCount=3 -t toolchains.xml
On 2026/03/10 18:55:56 "Tak Lon (Stephen) Wu" wrote: > +1 > > * Signature: ok > * Checksum : failed > * Rat check (8.0.452 & 17.0.17): ok > - mvn clean apache-rat:check > * Built from source (8.0.452 & 17.0.17): ok > - mvn clean install -DskipTests > * Unit tests pass (8.0.452 & 17.0.17): ok > - mvn clean package -P runAllTests > -Dsurefire.rerunFailingTestsCount=3 > > -Stephen > > On Tue, Mar 10, 2026 at 10:35 AM Pankaj Kumar <[email protected]> > wrote: > > > +1 (binding) > > > > * Signature: ok > > * Checksum : failed > > * Rat check (17.0.11): ok > > - mvn clean apache-rat:check > > * Built from source (17.0.11): ok > > - mvn clean install -DskipTests > > * Unit tests pass (17.0.11): ok > > - mvn clean package -P runAllTests > > -Dsurefire.rerunFailingTestsCount=3 > > > > HBASE-29971 PR looks good to me. > > > > Regards, > > Pankaj > > > > On Tue, Mar 10, 2026 at 10:23 PM Andrew Purtell <[email protected]> > > wrote: > > > > > +1 (binding) > > > > > > * Signature: ok > > > * Checksum : failed > > > * Rat check (17.0.18): ok > > > - mvn clean apache-rat:check > > > * Built from source (17.0.18): ok > > > - mvn clean install -DskipTests > > > * Unit tests pass (17.0.18): ok > > > - mvn package -P runAllTests > > -Dsurefire.rerunFailingTestsCount=3 > > > > > > The output of the vote script shows signature as failed but the actual > > > status is > > > > > > gpg: Signature made Fri Mar 6 20:12:46 2026 PST > > > gpg: using RSA key > > E54BBE3E97CFA48AAF7647E7AAC933D79AD2AE49 > > > gpg: Good signature from "Duo Zhang (Apache9) <[email protected]>" > > > [unknown] > > > > > > Approved the PR for HBASE-29971. > > > > > > Once the thirdparty is released and the PR to consume it is merged we > > will > > > make another attempt at 2.5 and 2.6 release candidates. > > > > > > On Tue, Mar 10, 2026 at 4:40 AM Nick Dimiduk <[email protected]> > > wrote: > > > > > > > > +1 > > > > > > > > * Signature: ok > > > > * Checksum : failed > > > > * Rat check (25.0.2): ok > > > > - mvn clean apache-rat:check > > > > * Built from source (25.0.2): ok > > > > - mvn clean install -DskipTests > > > > * Unit tests pass (25.0.2): ok > > > > - mvn clean package -P runAllTests > > > > -Dsurefire.rerunFailingTestsCount=3 > > > > > > > > On Tue, Mar 10, 2026 at 7:01 AM Nihal Jain <[email protected]> > > wrote: > > > > > > > > > +1 > > > > > > > > > > * Signature: OK > > > > > * Checksum : OK > > > > > * Rat check (1.8.0_292 and 17.0.16): OK > > > > > - mvn clean apache-rat:check > > > > > * Build from source (1.8.0_292 and 17.0.16): OK > > > > > - mvn clean install -DskipTests > > > > > * Unit Tests (1.8.0_292 and 17.0.16): OK > > > > > - mvn clean package -P release -Dsurefire.rerunFailingTestsCount=3 > > > > > > > > > > Also, the draft PR in main repo for upgrading hbase-thirdparty to > > > 4.1.13 > > > > > looks good to me! > > > > > > > > > > Regards, > > > > > Nihal > > > > > > > > > > On 2026/03/09 01:50:54 Duo Zhang wrote: > > > > > > +1 from me. > > > > > > > > > > > > This is the draft PR for upgrading hbase main repo to > > > hbase-thirdparty > > > > > > 4.1.13, which is good, the failed UTs are not related. > > > > > > > > > > > > https://github.com/apache/hbase/pull/7869 > > > > > > > > > > > > And I also run a 10B ITBLL, although it failed at 9th round's > > > > > > generator job, I did not see any data corruption problems since the > > > > > > failure was memory pressure and too many full GCs. > > > > > > > > > > > > Let's finish this release and then make new hbase releases to > > resolev > > > > > > the security problems. > > > > > > > > > > > > Thanks. > > > > > > > > > > > > Duo Zhang <[email protected]> 于2026年3月7日周六 17:48写道： > > > > > > > > > > > > > > Please vote on this Apache hbase thirdparty release candidate, > > > > > > > hbase-thirdparty-4.1.13RC1 > > > > > > > > > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > > > > > > > > > [ ] +1 Release this package as Apache hbase thirdparty 4.1.13 > > > > > > > [ ] -1 Do not release this package because ... > > > > > > > > > > > > > > The tag to be voted on is 4.1.13RC1: > > > > > > > > > > > > > > https://github.com/apache/hbase-thirdparty/tree/4.1.13RC1 > > > > > > > > > > > > > > This tag currently points to git reference > > > > > > > > > > > > > > c4d13cdfbe20cb9cc3b96ce6d567e7f8ac6c2421 > > > > > > > > > > > > > > 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/hbase-thirdparty-4.1.13RC1/ > > > > > > > > > > > > > > Maven artifacts are available in a staging repository at: > > > > > > > > > > > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachehbase-1597/ > > > > > > > > > > > > > > Artifacts were signed with the 0x9AD2AE49 key which can be found > > > in: > > > > > > > > > > > > > > https://downloads.apache.org/hbase/KEYS > > > > > > > > > > > > > > To learn more about Apache hbase thirdparty, please see > > > > > > > > > > > > > > http://hbase.apache.org/ > > > > > > > > > > > > > > Thanks, > > > > > > > Your HBase Release Manager > > > > > >
