The staging repository is now https://repository.apache.org/content/repositories/orgapachehbase-1420/ . Should this vote pass, this is the repository that will be released.
This repo does not contain the unwanted .asc.asc files found earlier. Other staging repos have been dropped. On Fri, Dec 4, 2020 at 9:29 AM Andrew Purtell <apurt...@apache.org> wrote: > The temporary Maven repository is now available at > > > https://repository.apache.org/content/repositories/orgapachehbase-1416/ . > > On Thu, Dec 3, 2020 at 4:04 PM Andrew Purtell <apurt...@apache.org> wrote: > >> Please vote on this Apache hbase release candidate, hbase-2.4.0RC1 >> >> The VOTE will remain open for at least 72 hours. >> >> [ ] +1 Release this package as Apache hbase 2.4.0 >> [ ] -1 Do not release this package because ... >> >> The tag to be voted on is 2.4.0RC1: >> >> https://github.com/apache/hbase/tree/2.4.0RC1 >> >> 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.0RC1/ >> >> Customarily Maven artifacts would be available in a staging repository. >> Unfortunately I was forced to terminate the Maven deploy step after >> the upload ran for more than four hours and my build equipment >> needed to be relocated, with loss of network connectivity. This RC has >> been delayed long enough. A temporary Maven repository is not a >> requirement for a vote. I will retry Maven deploy tomorrow. I can >> promise the artifacts for this RC will be staged in Apache Nexus and >> ready for release well ahead of the earliest possible time this vote >> can complete. >> >> 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.0RC1/api_compare_2.4.0RC1_to_2.3.0.html >> >> The changes are mostly added methods, which conform to the compatibility >> guidelines for a new minor release. There is one change to the public >> Region interface that alters the return type of a method. This is >> equivalent to a removal then addition and can be a binary compatibility >> problem. However to your RM's eye the change looks intentional and is >> part of an API improvement project, and a compatibility method is not >> possible here because Java doesn't consider return type when deciding if >> one method signature duplicates another. >> >> To learn more about Apache HBase, please see >> >> http://hbase.apache.org/ >> >> Thanks, >> Your HBase Release Manager >> > > > -- > Best regards, > Andrew > > Words like orphans lost among the crosstalk, meaning torn from truth's > decrepit hands > - A23, Crosstalk > -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk
