+1,

I’v checked:

- Checksums and PGP signatures are valid for Binary & Source package.
- Source code artifacts have correct names matching the current release.
- License and Notice are correct in Binary & Source package.
- Go pass according to quick start.


Best Regards,
Von Gosling

> On Nov 21, 2019, at 7:51 PM, ShannonDing <[email protected]> wrote:
> 
> Hello RocketMQ Community,
> 
> 
> 
> This is the vote for 4.6.0 of Apache RocketMQ.
> 
> 
> 
> This release adds a lightweight pull consumer and added fully support for 
> IPv6 environments. This release also provides a request-reply feature to 
> support micro-services. In addition, this release also fixed some issues and 
> further improved the stability of related modules such as transaction 
> messages and abnormal recovery.
> 
> 
> 
> The artifacts:
> 
> https://dist.apache.org/repos/dist/dev/rocketmq/4.6.0-rc1/ 
> <https://dist.apache.org/repos/dist/dev/rocketmq/4.6.0-rc1/>
> 
> The staging repo:
> 
> https://repository.apache.org/content/repositories/orgapacherocketmq-1033/ 
> <https://repository.apache.org/content/repositories/orgapacherocketmq-1033/>
> 
> Git tag for the release:
> 
> https://github.com/apache/rocketmq/tree/release-4.6.0 
> <https://github.com/apache/rocketmq/tree/release-4.6.0>
> 
> Hash for the release tag:
> 
> d1b4e47c26576cf4fa543bbdd8c6f09643220bed
> 
> 
> 
> Release Notes:
> 
> https://rocketmq.apache.org/release_notes/release-notes-4.6.0/ 
> <https://rocketmq.apache.org/release_notes/release-notes-4.6.0/>
> 
> The artifacts have been signed with Key :
> 
> BC9E172DE1BA5B24EBB4A628177B55985D75751B, which can be found in the keys file:
> 
> https://dist.apache.org/repos/dist/dev/rocketmq/KEYS 
> <https://dist.apache.org/repos/dist/dev/rocketmq/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 RocketMQ Team
> 
> 
> 
> 

Reply via email to