+0 * Signature: OK * Checksum : OK * Rat check (1.8.0_381): OK - mvn clean apache-rat:check * Build from source (1.8.0_381): OK - mvn clean install -DskipTests * Unit Tests (1.8.0_381): OK - mvn clean package -P release -Dsurefire.rerunFailingTestsCount=3
But I see that https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty-4.1.6RC0/RELEASENOTES.md is empty for the current release. Is this enough to sink an RC? Or can this be replaced in place? Consider my vote as +1, if we are good. Regards Nihal On Tue, 27 Feb 2024, 21:37 Nick Dimiduk, <ndimi...@apache.org> wrote: > Please vote on this Apache hbase thirdparty release candidate, > hbase-thirdparty-4.1.6RC0 > > The VOTE will remain open for at least 72 hours. > > [ ] +1 Release this package as Apache hbase thirdparty 4.1.6 > [ ] -1 Do not release this package because ... > > The tag to be voted on is 4.1.6RC0: > > https://github.com/apache/hbase-thirdparty/tree/4.1.6RC0 > > This tag currently points to git reference > > b1a8d26f5eb9f45d4069d1fdd909d0d22123950c > > 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.6RC0/ > > Maven artifacts are available in a staging repository at: > > https://repository.apache.org/content/repositories/orgapachehbase-1533/ > > Artifacts were signed with the 0xEF4EBF27 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 >
