You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Sean Busbey <bu...@apache.org> on 2019/09/25 16:40:58 UTC

[RESULT] Re: [VOTE] HBase Thirdparty 3.0.0 RC0

With four +1 votes (three binding), this vote passes.

my thanks to everyone who pitched in!

On Sun, Sep 22, 2019 at 12:19 AM Sean Busbey <bu...@apache.org> wrote:
>
> Please consider the following for the 3.0.0 release of Apache HBase Thirdparty.
>
> The only change since our prior 2.2.1 release moves our relocated GSON
> library into its own artifact and ensures that that artifact can be
> used with JDK7 for branch-1 releases.
>
> Source artifact, signatures, checksums, and changes are available at:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-thirdparty-3.0.0-RC0/
>
> The release was made against tag 3.0.0RC0 which currently points at ref
> 7bc3b10d118dd171c76ef7a4e8e79e91e99b740e
>
> Everything is signed with my key '0D80DB7C' which can be found here:
>
>  https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> Maven staging repository is available at:
>
>  https://repository.apache.org/content/repositories/orgapachehbase-1350/
>
> Since these artifacts don't really show up downstream until they're
> used in a main HBase release, I'd like to only run this vote as long
> as it takes to get enough binding votes if folks don't mind. I figure
> it's relatively easy for us to roll forward with another HBase
> Thirdparty release if something comes up while trying to use it in a
> main HBase release candidate.
>
> As of this email the relevant artifact sha512 checksum(s) are:
>
> hbase-thirdparty-3.0.0-src.tar.gz:
> B6BA18F5 515E9B18 3079F7A3 65E68462 CC2571DB
> 1A078141 06A94652 D5276713 E0C54FF5 1CC1C16D
> B0E28F4A BD3D37A2 2106C295 B250F153 4FD172ED
> CE3489FD