Thank you for verifying. Any contributions to the rocketmq-spring project are highly welcome.
"Divyansh Agrawal" <divyanshag1...@gmail.com>写道： > Hi Rongtong Jin and the RocketMQ community, > I reviewed the release artifacts and was able to successfully build the > source package. The tests ran fine on my local setup. > Although I am not a voting member yet, I appreciate the effort behind this > release and look forward to contributing more. > Best regards, > Divyansh > > > ________________________________ > From: jinrongto...@163.com <jinrongto...@163.com> on behalf of jinrongtong > <jinrongt...@apache.org> > Sent: 17 March 2025 14:52 > To: dev@rocketmq.apache.org <dev@rocketmq.apache.org> > Cc: us...@rocketmq.apache.org <us...@rocketmq.apache.org> > Subject: Re:Re:[VOTE]Release Apache RocketMQ Spring 2.3.3 RC1 > > +1 > At 2025-03-17 17:09:47, "ShannonDing" <ding...@apache.org> wrote: > >+1 > > > > > > > > > >At 2025-03-14 11:24:21, "jinrongtong" <jinrongt...@apache.org> wrote: > > > >Hello RocketMQ Community, > > > > > > > > > >This is the vote for the 2.3.3 release of Apache RocketMQ-Spring. > > > > > > > > > >The artifacts: > > > >https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-spring/2.3.3-rc1/ > > > > > > > > > >The staging repo: > > > >https://repository.apache.org/content/repositories/orgapacherocketmq-1340 > > > > > > > > > >Git tag for the release: > > > >https://github.com/apache/rocketmq-spring/releases/tag/rocketmq-spring-all-2.3.3 > > > > > >Release Notes: > >https://rocketmq.apache.org/zh/release-notes/2025/03/14/release-notes-rocketmq-spring-2.3.3 > > > > > >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 > > > > > > > > > > > > > >
