You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by 徐江 <jo...@163.com> on 2019/09/03 03:20:27 UTC
Re:[RESTART][VOTE][#1] Release Apache RocketMQ Client CPP 1.2.3
RC2.
+1 approve
Checklist for reference,
Note that this is not official policy but may help with checking releases.
Fill in the following:
[Y] Checksums and PGP signatures are valid for Source package.
[Y] Checksums and PGP signatures are valid for Binary package.
[Y] Source code artifacts have correct names matching the current release.
[Y] Binary artifacts have correct names matching the current release.
[Y] License and Notice are correct in source package.
[Y] License and Notice are correct in binary package.
[Y] All files have license headers in source package if necessary.
[Y] No compiled archives bundled in source archive.
[Y] Hash and Tag in GitHub repo is matching the current artifacts.
[Y] The code can be built success in the source package.
And any other check point is welcomed and please feel free to reply to this email, we sincerely hope to your feedback.
At 2019-08-29 19:40:31, "ShannonDing" <di...@apache.org> wrote:
Hello RocketMQ Community,
This is the vote for version 1.2.3 of Apache RocketMQ Client CPP.
This release included main futures below:
Support transaction message.
Support C style batch message sending.
Support getting error information when C API returns false.
Polish the TCP transport layer.
Remove useless code and fix compile warnings.
For detail info, please see the release note.
The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/1.2.3-rc2/
Git tag for the release:
https://github.com/apache/rocketmq-client-cpp/tree/release-1.2.3
Hash for the release tag:
dcf3a1f0b4c2b9826a391e40d053889ee4fafd91
Release Notes:
http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-1.2.3/
The artifacts have been signed with Key :
BBC3FBA877D30832E2FBC8F901B994150CD1E262, 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.
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
[RESULT] [RESTART][VOTE][#1] Release Apache RocketMQ Client CPP
1.2.3 RC2.
Posted by ShannonDing <di...@apache.org>.
Hello RocketMQ Community,
The Apache RocketMQ vote is now closed and has passed with [3] binding +1s,[3] non-binding +1s and no 0 or -1:
*Binding votes +1s:*
heng du (duhengforever)
ShannonDing(dinglei)
Li qipeng(wlliqipeng)
*Non-binding votes +1s:*
jonnxu
jinrongtong16
Yin James
The release will be published soon.
Thanks,
The Apache RocketMQ Team
On 09/6/2019 11:45，heng du<du...@gmail.com> wrote：
+1, I have checked
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 the source package.
All files have license headers in source package if necessary.
徐江 <jo...@163.com> 于2019年9月3日周二 上午11:20写道：
+1 approve
Checklist for reference,
Note that this is not official policy but may help with checking releases.
Fill in the following:
[Y] Checksums and PGP signatures are valid for Source package.
[Y] Checksums and PGP signatures are valid for Binary package.
[Y] Source code artifacts have correct names matching the current release.
[Y] Binary artifacts have correct names matching the current release.
[Y] License and Notice are correct in source package.
[Y] License and Notice are correct in binary package.
[Y] All files have license headers in source package if necessary.
[Y] No compiled archives bundled in source archive.
[Y] Hash and Tag in GitHub repo is matching the current artifacts.
[Y] The code can be built success in the source package.
And any other check point is welcomed and please feel free to reply to
this email, we sincerely hope to your feedback.
At 2019-08-29 19:40:31, "ShannonDing" <di...@apache.org> wrote:
Hello RocketMQ Community,
This is the vote for version 1.2.3 of Apache RocketMQ Client CPP.
This release included main futures below:
Support transaction message.
Support C style batch message sending.
Support getting error information when C API returns false.
Polish the TCP transport layer.
Remove useless code and fix compile warnings.
For detail info, please see the release note.
The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/1.2.3-rc2/
Git tag for the release:
https://github.com/apache/rocketmq-client-cpp/tree/release-1.2.3
Hash for the release tag:
dcf3a1f0b4c2b9826a391e40d053889ee4fafd91
Release Notes:
http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-1.2.3/
The artifacts have been signed with Key :
BBC3FBA877D30832E2FBC8F901B994150CD1E262, 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.
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
Re: [RESTART][VOTE][#1] Release Apache RocketMQ Client CPP 1.2.3
RC2.
Posted by ShannonDing <di...@apache.org>.
+1, checklist as below:
[ OK] Checksums and PGP signatures are valid for Source package.
[ OK] Checksums and PGP signatures are valid for Binary package.
[ OK] Source code artifacts have correct names matching the current release.
[ OK] Binary artifacts have correct names matching the current release.
[ OK] License and Notice are correct in source package.
[ OK] License and Notice are correct in binary 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 is matching the current artifacts.
On 09/6/2019 11:45，heng du<du...@gmail.com> wrote：
+1, I have checked
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 the source package.
All files have license headers in source package if necessary.
徐江 <jo...@163.com> 于2019年9月3日周二 上午11:20写道：
+1 approve
Checklist for reference,
Note that this is not official policy but may help with checking releases.
Fill in the following:
[Y] Checksums and PGP signatures are valid for Source package.
[Y] Checksums and PGP signatures are valid for Binary package.
[Y] Source code artifacts have correct names matching the current release.
[Y] Binary artifacts have correct names matching the current release.
[Y] License and Notice are correct in source package.
[Y] License and Notice are correct in binary package.
[Y] All files have license headers in source package if necessary.
[Y] No compiled archives bundled in source archive.
[Y] Hash and Tag in GitHub repo is matching the current artifacts.
[Y] The code can be built success in the source package.
And any other check point is welcomed and please feel free to reply to
this email, we sincerely hope to your feedback.
At 2019-08-29 19:40:31, "ShannonDing" <di...@apache.org> wrote:
Hello RocketMQ Community,
This is the vote for version 1.2.3 of Apache RocketMQ Client CPP.
This release included main futures below:
Support transaction message.
Support C style batch message sending.
Support getting error information when C API returns false.
Polish the TCP transport layer.
Remove useless code and fix compile warnings.
For detail info, please see the release note.
The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/1.2.3-rc2/
Git tag for the release:
https://github.com/apache/rocketmq-client-cpp/tree/release-1.2.3
Hash for the release tag:
dcf3a1f0b4c2b9826a391e40d053889ee4fafd91
Release Notes:
http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-1.2.3/
The artifacts have been signed with Key :
BBC3FBA877D30832E2FBC8F901B994150CD1E262, 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.
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
Re: [RESTART][VOTE][#1] Release Apache RocketMQ Client CPP 1.2.3
RC2.
Posted by ShannonDing <di...@apache.org>.
+1, checklist as below:
[ OK] Checksums and PGP signatures are valid for Source package.
[ OK] Checksums and PGP signatures are valid for Binary package.
[ OK] Source code artifacts have correct names matching the current release.
[ OK] Binary artifacts have correct names matching the current release.
[ OK] License and Notice are correct in source package.
[ OK] License and Notice are correct in binary 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 is matching the current artifacts.
On 09/6/2019 11:45，heng du<du...@gmail.com> wrote：
+1, I have checked
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 the source package.
All files have license headers in source package if necessary.
徐江 <jo...@163.com> 于2019年9月3日周二 上午11:20写道：
+1 approve
Checklist for reference,
Note that this is not official policy but may help with checking releases.
Fill in the following:
[Y] Checksums and PGP signatures are valid for Source package.
[Y] Checksums and PGP signatures are valid for Binary package.
[Y] Source code artifacts have correct names matching the current release.
[Y] Binary artifacts have correct names matching the current release.
[Y] License and Notice are correct in source package.
[Y] License and Notice are correct in binary package.
[Y] All files have license headers in source package if necessary.
[Y] No compiled archives bundled in source archive.
[Y] Hash and Tag in GitHub repo is matching the current artifacts.
[Y] The code can be built success in the source package.
And any other check point is welcomed and please feel free to reply to
this email, we sincerely hope to your feedback.
At 2019-08-29 19:40:31, "ShannonDing" <di...@apache.org> wrote:
Hello RocketMQ Community,
This is the vote for version 1.2.3 of Apache RocketMQ Client CPP.
This release included main futures below:
Support transaction message.
Support C style batch message sending.
Support getting error information when C API returns false.
Polish the TCP transport layer.
Remove useless code and fix compile warnings.
For detail info, please see the release note.
The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/1.2.3-rc2/
Git tag for the release:
https://github.com/apache/rocketmq-client-cpp/tree/release-1.2.3
Hash for the release tag:
dcf3a1f0b4c2b9826a391e40d053889ee4fafd91
Release Notes:
http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-1.2.3/
The artifacts have been signed with Key :
BBC3FBA877D30832E2FBC8F901B994150CD1E262, 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.
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
[RESULT] [RESTART][VOTE][#1] Release Apache RocketMQ Client CPP
1.2.3 RC2.
Posted by ShannonDing <di...@apache.org>.
Hello RocketMQ Community,
The Apache RocketMQ vote is now closed and has passed with [3] binding +1s,[3] non-binding +1s and no 0 or -1:
*Binding votes +1s:*
heng du (duhengforever)
ShannonDing(dinglei)
Li qipeng(wlliqipeng)
*Non-binding votes +1s:*
jonnxu
jinrongtong16
Yin James
The release will be published soon.
Thanks,
The Apache RocketMQ Team
On 09/6/2019 11:45，heng du<du...@gmail.com> wrote：
+1, I have checked
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 the source package.
All files have license headers in source package if necessary.
徐江 <jo...@163.com> 于2019年9月3日周二 上午11:20写道：
+1 approve
Checklist for reference,
Note that this is not official policy but may help with checking releases.
Fill in the following:
[Y] Checksums and PGP signatures are valid for Source package.
[Y] Checksums and PGP signatures are valid for Binary package.
[Y] Source code artifacts have correct names matching the current release.
[Y] Binary artifacts have correct names matching the current release.
[Y] License and Notice are correct in source package.
[Y] License and Notice are correct in binary package.
[Y] All files have license headers in source package if necessary.
[Y] No compiled archives bundled in source archive.
[Y] Hash and Tag in GitHub repo is matching the current artifacts.
[Y] The code can be built success in the source package.
And any other check point is welcomed and please feel free to reply to
this email, we sincerely hope to your feedback.
At 2019-08-29 19:40:31, "ShannonDing" <di...@apache.org> wrote:
Hello RocketMQ Community,
This is the vote for version 1.2.3 of Apache RocketMQ Client CPP.
This release included main futures below:
Support transaction message.
Support C style batch message sending.
Support getting error information when C API returns false.
Polish the TCP transport layer.
Remove useless code and fix compile warnings.
For detail info, please see the release note.
The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/1.2.3-rc2/
Git tag for the release:
https://github.com/apache/rocketmq-client-cpp/tree/release-1.2.3
Hash for the release tag:
dcf3a1f0b4c2b9826a391e40d053889ee4fafd91
Release Notes:
http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-1.2.3/
The artifacts have been signed with Key :
BBC3FBA877D30832E2FBC8F901B994150CD1E262, 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.
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
Re: [RESTART][VOTE][#1] Release Apache RocketMQ Client CPP 1.2.3 RC2.
Posted by heng du <du...@gmail.com>.
+1, I have checked
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 the source package.
All files have license headers in source package if necessary.
徐江 <jo...@163.com> 于2019年9月3日周二 上午11:20写道：
> +1 approve
>
>
>
> Checklist for reference,
>
> Note that this is not official policy but may help with checking releases.
>
> Fill in the following:
>
> [Y] Checksums and PGP signatures are valid for Source package.
>
> [Y] Checksums and PGP signatures are valid for Binary package.
>
> [Y] Source code artifacts have correct names matching the current release.
>
> [Y] Binary artifacts have correct names matching the current release.
>
> [Y] License and Notice are correct in source package.
>
> [Y] License and Notice are correct in binary package.
>
> [Y] All files have license headers in source package if necessary.
>
> [Y] No compiled archives bundled in source archive.
>
> [Y] Hash and Tag in GitHub repo is matching the current artifacts.
>
> [Y] The code can be built success in the source package.
>
> And any other check point is welcomed and please feel free to reply to
> this email, we sincerely hope to your feedback.
>
>
>
>
> At 2019-08-29 19:40:31, "ShannonDing" <di...@apache.org> wrote:
>
>
> Hello RocketMQ Community,
>
> This is the vote for version 1.2.3 of Apache RocketMQ Client CPP.
>
>
>
>
> This release included main futures below:
>
> Support transaction message.
> Support C style batch message sending.
> Support getting error information when C API returns false.
> Polish the TCP transport layer.
> Remove useless code and fix compile warnings.
>
> For detail info, please see the release note.
>
>
>
>
> The artifacts:
>
>
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/1.2.3-rc2/
>
>
>
>
> Git tag for the release:
>
> https://github.com/apache/rocketmq-client-cpp/tree/release-1.2.3
>
>
>
>
> Hash for the release tag:
>
> dcf3a1f0b4c2b9826a391e40d053889ee4fafd91
>
>
>
>
> Release Notes:
>
>
> http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-1.2.3/
>
>
>
>
> The artifacts have been signed with Key :
>
> BBC3FBA877D30832E2FBC8F901B994150CD1E262, 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.
>
> 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
>
>
>
Re: [RESTART][VOTE][#1] Release Apache RocketMQ Client CPP 1.2.3 RC2.
Posted by heng du <du...@gmail.com>.
+1, I have checked
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 the source package.
All files have license headers in source package if necessary.
徐江 <jo...@163.com> 于2019年9月3日周二 上午11:20写道：
> +1 approve
>
>
>
> Checklist for reference,
>
> Note that this is not official policy but may help with checking releases.
>
> Fill in the following:
>
> [Y] Checksums and PGP signatures are valid for Source package.
>
> [Y] Checksums and PGP signatures are valid for Binary package.
>
> [Y] Source code artifacts have correct names matching the current release.
>
> [Y] Binary artifacts have correct names matching the current release.
>
> [Y] License and Notice are correct in source package.
>
> [Y] License and Notice are correct in binary package.
>
> [Y] All files have license headers in source package if necessary.
>
> [Y] No compiled archives bundled in source archive.
>
> [Y] Hash and Tag in GitHub repo is matching the current artifacts.
>
> [Y] The code can be built success in the source package.
>
> And any other check point is welcomed and please feel free to reply to
> this email, we sincerely hope to your feedback.
>
>
>
>
> At 2019-08-29 19:40:31, "ShannonDing" <di...@apache.org> wrote:
>
>
> Hello RocketMQ Community,
>
> This is the vote for version 1.2.3 of Apache RocketMQ Client CPP.
>
>
>
>
> This release included main futures below:
>
> Support transaction message.
> Support C style batch message sending.
> Support getting error information when C API returns false.
> Polish the TCP transport layer.
> Remove useless code and fix compile warnings.
>
> For detail info, please see the release note.
>
>
>
>
> The artifacts:
>
>
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/1.2.3-rc2/
>
>
>
>
> Git tag for the release:
>
> https://github.com/apache/rocketmq-client-cpp/tree/release-1.2.3
>
>
>
>
> Hash for the release tag:
>
> dcf3a1f0b4c2b9826a391e40d053889ee4fafd91
>
>
>
>
> Release Notes:
>
>
> http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-1.2.3/
>
>
>
>
> The artifacts have been signed with Key :
>
> BBC3FBA877D30832E2FBC8F901B994150CD1E262, 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.
>
> 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
>
>
>