+1

On Fri, Mar 1, 2024 at 12:35 PM Gaoyang Cai <ca...@apache.org> wrote:

>
> +1
>
>
>
>
>
>
> At 2024-02-20 14:16:45, "jinrongtong" <jinrongt...@apache.org> wrote:
> >Hello RocketMQ Community,
> >
> >
> >
> >This is the vote for the 2.3.0 release of Apache RocketMQ-Spring.
> >
> >
> >
> >The artifacts:
> >
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-spring/2.3.0-rc1/
> >
> >
> >The staging repo:
> >https://repository.apache.org/content/repositories/orgapacherocketmq-1310
> >
> >
> >Git tag for the release:
> >
> https://github.com/apache/rocketmq-spring/releases/tag/rocketmq-spring-all-2.3.0
> >
> >
> >Hash for the release tag:
> >8b4a5417e86d1f22e60ac62d37c60104172be423
> >
> >
> >Release Notes:
> >
> https://rocketmq.apache.org/zh/release-notes/2024/02/19/release-notes-rocketmq-spring-2.3.0
> >
> >
> >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 an official policy but may help with checking
> releases.
> >
> >
> >Fill in the following:
> >[ ]  Checksums and PGP signatures are valid for source package.
> >[ ]  Source code artifacts have correct names matching the current
> release.
> >[ ]  License and Notice are correct in source package.
> >[ ]  All files have license headers in source package if necessary.
> >[ ]  No compiled archives bundled in source archive.
> >[ ]  Hash and Tag in GitHub repo are matching the current artifacts.
> >[ ]  The code can be built success in the source package.
> >
> >
> >And any other checkpoint is welcomed and please feel free to reply to
> this email, we sincerely hope for your feedback.
> >The vote will be open for at least 72 hours or until a necessary number
> of votes are reached.
> >
> >
> >Please vote accordingly:
> >[ ] +1 approve
> >[ ] +0 no opinion
> >[ ] -1 disapprove with the reason
> >
> >
> >
> >
> >Thanks,
> >Rongtong Jin
>

Reply via email to