The new staging repo address is

https://repository.apache.org/content/repositories/orgapachehbase-1378

The vote will be extended for another 24 hours.

Thanks.

张铎(Duo Zhang) <[email protected]> 于2019年11月28日周四 下午8:30写道:

> I used to think we only need to change the script but the patch in
> HBASE-23337 requires changing the pom...
>
> Then let me reuse this RC tag and deploy a new staging repo...
>
> Will be back once I'm done...
>
> 张铎(Duo Zhang) <[email protected]> 于2019年11月25日周一 上午10:00写道:
>
>> Also confirm that the staging repo missed all the shaded artifacts.
>>
>> Let's roll a RC1 after we find out the reason.
>>
>> Sean Busbey <[email protected]> 于2019年11月25日周一 上午8:03写道:
>>
>>> -1
>>>
>>>
>>>  the staged maven repo is missing the shaded client artifacts.
>>>
>>> On Wed, Nov 20, 2019, 00:15 Duo Zhang <[email protected]> wrote:
>>>
>>> > Please vote on this Apache hbase release candidate,
>>> > hbase-2.1.8RC0
>>> >
>>> > The VOTE will remain open for at least 72 hours.
>>> >
>>> > [ ] +1 Release this package as Apache hbase 2.1.8
>>> > [ ] -1 Do not release this package because ...
>>> >
>>> > The tag to be voted on is 2.1.8RC0:
>>> >
>>> > https://github.com/apache/hbase/tree/2.1.8RC0
>>> >
>>> > 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.1.8RC0/
>>> >
>>> > Maven artifacts are available in a staging repository at:
>>> >
>>> >
>>> https://repository.apache.org/content/repositories/orgapachehbase-1372/
>>> >
>>> > Artifacts were signed with the 9AD2AE49 key which can be found in:
>>> >
>>> >  https://dist.apache.org/repos/dist/release/hbase/KEYS
>>> >
>>> > 2.1.8 includes ~59 bug and improvement fixes done since the 2.1.7.
>>> > We upgrade jackson to 2.9.10.1 due to CVE-2019-16942 and
>>> CVE-2019-16943.
>>> >
>>> >  To learn more about apache hbase, please see
>>> > http://hbase.apache.org/
>>> >
>>> > Thanks,
>>> > Your HBase Release Manager
>>> >
>>>
>>

Reply via email to