>> The staging repo:
>> https://repository.apache.org/content/repositories/orgapachedubbo-1370
> 
> 
> The staging repo should be 
> https://repository.apache.org/content/repositories/orgapachebeam-1371/

Sorry, I pasted the wrong staging link. I think there’s still no available 
staging repo for this release yet.

Regards,
Jun Liu



> On Mar 14, 2024, at 2:56 PM, Jun Liu <ken.lj...@gmail.com> wrote:
> 
> 
> 
>> Git tag for the release:
>> https://github.com/apache/dubbo-spi-extensions/tree/3.2.0-release
>> 
>> Hash for the release tag:
>> 8c8e9126c318c810a2c290562ef47eb545d85cbd
> 
> The hash points to the latest commit in 
> https://github.com/apache/dubbo-spi-extensions/tree/v3.2.0, so we should put 
> the tag link instead of the branch link.
> 
> 
>> The staging repo:
>> https://repository.apache.org/content/repositories/orgapachedubbo-1370
> 
> 
> The staging repo should be 
> https://repository.apache.org/content/repositories/orgapachebeam-1371/
> 
> 
> Regards,
> Jun Liu
> 
> 
> 
>> On Mar 11, 2024, at 6:43 PM, songxiaosheng <songxiaosh...@apache.org> wrote:
>> 
>> Hello Dubbo Community,
>> 
>> This is a call for vote to release Apache Dubbo SPI Extensions 3.2.0 RC1.
>> 
>> The release candidates:
>> https://dist.apache.org/repos/dist/dev/dubbo/dubbo-spi-extensions/3.2.0/
>> 
>> The staging repo:
>> https://repository.apache.org/content/repositories/orgapachedubbo-1370
>> 
>> Git tag for the release:
>> https://github.com/apache/dubbo-spi-extensions/tree/3.2.0-release
>> 
>> Hash for the release tag:
>> 8c8e9126c318c810a2c290562ef47eb545d85cbd
>> 
>> Release Notes:
>> https://github.com/apache/dubbo-spi-extensions/releases/tag/v3.2.0
>> 
>> The artifacts have been signed with Key :
>> 68AA0968D1C406C6, which can be found in the
>> keys file:
>> https://dist.apache.org/repos/dist/dev/dubbo/KEYS
>> 
>> The vote will be open for at least 72 hours or until necessary number
>> of votes are reached.
>> 
>> Please vote accordingly:
>> 
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove with the reason
>> 
>> Thanks,
>> The Apache Dubbo Team
> 

Reply via email to