+1

On Tue, Jun 13, 2023 at 3:01 PM jinrongtong <jinrongt...@apache.org> wrote:

> Hello RocketMQ Community,
>
> This is the vote for 5.1.2 of Apache RocketMQ.
>
> This release fixes some bugs to enhance stability.
>
> The artifacts:
> https://dist.apache.org/repos/dist/dev/rocketmq/5.1.2-rc1/
>
> The staging repo:
> https://repository.apache.org/content/repositories/orgapacherocketmq-1229
>
> Git tag for the release:
> https://github.com/apache/rocketmq/tree/release-5.1.2
>
> Hash for the release tag:
> 749967baa82bafb155353351154b5c6ace095574
>
>
>
>
> Release Notes:
> https://rocketmq.apache.org/zh/release-notes/2023/06/12/5.1.2/
>
>
>
> The artifacts have been signed with Key :
> EC9F268B4C20590138B11FE701420E4292296EAE, which can be found in the keys
> file:
> https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
>
> Checklist for reference,
> Note that this is not official policy but may help with checking releases.
> Fill in the following:
>
> []  Checksums and PGP signatures are valid for Source package.
> []  Checksums and PGP signatures are valid for Binary package.
> []  Source code artifacts have correct names matching the current release.
> []  Binary artifacts have correct names matching the current release.
> []  License and Notice are correct in source package.
> []  License and Notice are correct in binary package.
> []  All files have license headers in source package if necessary.
> []  No compiled archives bundled in source archive.
> []  Hash and Tag in GitHub repo is matching the current artifacts.
> []  The code can be built success in the source package.
> []  Start nameserver and broker according to the quick-start
> []  Run clusterList command to see if the version is correct
>
> And any other check point is welcomed and please feel free to reply to
> this email, we sincerely hope to your feedback.
>
> 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