I don't know anymore :) Maybe it was my browser doing some shenanigans
when it was downloading the bits. dist/release looks fine. Thanks!
On 1/25/20 12:15 PM, Stack wrote:
Which .txt are you referring to Josh? I see only .sha512 (could be going
blind though)
Thanks,
S
On Fri, Jan 24, 2020 at 1:21 PM Josh Elser <[email protected]> wrote:
+1 (binding)
According to the release policy[1], the checksum file must be renamed
from .txt to .sha512.
Certainly doesn't require a new RC or some such nonsense. A careful `svn
mv` on the vote passing is just fine.
[1] https://www.apache.org/dev/release-distribution.html#sigs-and-sums
On 1/22/20 8:55 PM, Stack wrote:
Please vote on this Apache hbase thirdparty release candidate,
hbase-thirdparty-3.2.0RC0
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache hbase thirdparty 3.2.0
[ ] -1 Do not release this package because ...
The tag to be voted on is 3.2.0RC0:
https://github.com/apache/hbase-thirdparty/tree/3.2.0RC0
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/3.2.0RC0/
Maven artifacts are available in a staging repository at:
https://repository.apache.org/content/repositories//
Artifacts were signed with the [email protected] key which can be found
in:
https://dist.apache.org/repos/dist/release/hbase/KEYS
To learn more about apache hbase thirdparty, please see
http://hbase.apache.org/
Thanks,
Your HBase Release Manager
