+1
caigy <csgyt...@163.com> 于2023年2月6日周一 20:28写道： > > +1 （Non-binding） > > I checked: > > [OK] Checksums and PGP signatures are valid for source package. > [OK] Source code artifacts have correct names matching the current release. > [OK] License and Notice are correct in source package. > [OK] All files have license headers in source package if necessary. > [OK] No compiled archives bundled in source archive. > [OK] Hash and Tag in GitHub repo are matching the current artifacts. > [OK] The code can be built success in the source package. > > > > > > > At 2023-02-06 15:13:43, "jinrongtong" <jinrongt...@apache.org> wrote: > >Hi All, the correct release notes is > >https://rocketmq.apache.org/release-notes/2023/02/06/release-notes-rocketmq-spring-2.2.3 > > > > > > > >At 2023-02-06 13:36:43, "jinrongtong" <jinrongt...@apache.org> wrote: > > > >Hello RocketMQ Community, > > > >This is the vote for the 2.2.3 release of Apache RocketMQ-Spring. > > > >The artifacts: > >https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-spring/2.2.3-rc1/ > > > > > >The staging repo: > >https://repository.apache.org/content/repositories/orgapacherocketmq-1138 > > > > > >Git tag for the release: > >https://github.com/apache/rocketmq-spring/releases/tag/rocketmq-spring-all-2.2.3 > > > > > >Hash for the release tag: > >940132c8c3b6d5896a902bb76d9c90cd23527737 > > > > > >Release Notes: > >http://rocketmq.apache.org/release_notes/release-notes-rocketmq-spring-2.2.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
