Had a brief tangent with Peter in backchat about branch-2.2 and how it's
not on current thirdparty releases, but, now that I understand where we
are, I'm good with rc0.
* Sigs/xsums good
* rat-check fine
* running dev-tests w/o issue against branch-2 (since Duo built master)
* tried to build phoenix too, but ran into other issues (see
aforementioned tangent)
I'm OK with this as it is, but am also OK if we fix releasenotes. IMO,
we could just fix releasenotes.md when doing copy from dist/dev to
dist/release (don't need new jars -- they aren't changing).
+1 (binding)
On 4/25/20 10:58 AM, Peter Somogyi wrote:
Please vote on this Apache hbase thirdparty release candidate,
hbase-thirdparty-3.3.0RC0
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache hbase thirdparty 3.3.0
[ ] -1 Do not release this package because ...
The tag to be voted on is 3.3.0RC0:
https://github.com/apache/hbase-thirdparty/tree/3.3.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.3.0RC0/
Maven artifacts are available in a staging repository at:
https://repository.apache.org/content/repositories/orgapachehbase-1388/
Artifacts were signed with the psomo...@apache.org 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
