You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by ShannonDing <di...@apache.org> on 2020/04/07 01:44:04 UTC

[VOTE]Release Apache RocketMQ Client CPP 2.2.0 RC1.

Hello RocketMQ Community,
This is the vote for version 2.2.0 of Apache RocketMQ Client CPP.
This release support TLS mode with OpenSSL for sending messages in sync model and consuming messages by push model and use an separate producer to send trace messages. 


The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/2.2.0-rc1/
Git tag for the release:
https://github.com/apache/rocketmq-client-cpp/releases/tag/2.2.0
Hash for the release tag:
6579eb637f81bca29f59f1e8645897a8c12a0871
Release Notes:
http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-2.2.0/
The artifacts have been signed with Key :
BC9E172DE1BA5B24EBB4A628177B55985D75751B, 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][VOTE]Release Apache RocketMQ Client CPP 2.2.0 RC1.

Posted by ShannonDing <di...@apache.org>.
Hello RocketMQ Community,


The Apache RocketMQ Client CPP 2.2.0 vote is now closed and has passed with [4] binding +1s, [0] non-binding +1s and no 0 or -1:


*Binding votes +1s:*


Gosling Von (vongosling@apache.org)
ShannonDing(dinglei@apache.org)
Jin Rongtong(jinrongtong@apache.org)
Li Qipeng(wlliqipeng@apache.org)
*Non-binding votes +1s:*


The release will be published soon.


Thanks,
The Apache RocketMQ Team

Re: [VOTE]Release Apache RocketMQ Client CPP 2.2.0 RC1.

Posted by vongosling <fe...@gmail.com>.
Hi,

+1 (binding)

I checked:
- signatures and hashes fine
- LICENSE and NOTICE looks OK
- All necessary files have license headers
- No compiled archives bundled in the source archive
- Release note seems clear for me

Best Regards,
Von Gosling


金融通 <ji...@mails.ucas.ac.cn> 于2020年4月10日周五 下午3:48写道:

> +1,
> I checked
> -  Checksums and PGP signatures are valid for Source package.
> -  Checksums and PGP signatures are valid for Binary package.
> -  Hash and Tag in GitHub repo is matching the current artifacts.
> -  License and Notice are correct in source package.
> -  License and Notice are correct in binary package.
>
>
>
> &gt; -----原始邮件-----
> &gt; 发件人: ShannonDing <di...@apache.org>
> &gt; 发送时间: 2020-04-07 09:44:04 (星期二)
> &gt; 收件人: "dev@rocketmq.apache.org" <de...@rocketmq.apache.org>
> &gt; 抄送:
> &gt; 主题: [VOTE]Release Apache RocketMQ Client CPP 2.2.0 RC1.
> &gt;
> &gt; Hello RocketMQ Community,
> &gt; This is the vote for version 2.2.0 of Apache RocketMQ Client CPP.
> &gt; This release support TLS mode with OpenSSL for sending messages in
> sync model and consuming messages by push model and use an separate
> producer to send trace messages.
> &gt;
> &gt;
> &gt; The artifacts:
> &gt;
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/2.2.0-rc1/
> &gt
> <https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/2.2.0-rc1/&gt>;
> Git tag for the release:
> &gt; https://github.com/apache/rocketmq-client-cpp/releases/tag/2.2.0
> &gt <https://github.com/apache/rocketmq-client-cpp/releases/tag/2.2.0&gt>;
> Hash for the release tag:
> &gt; 6579eb637f81bca29f59f1e8645897a8c12a0871
> &gt; Release Notes:
> &gt;
> http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-2.2.0/
> &gt
> <http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-2.2.0/&gt>;
> The artifacts have been signed with Key :
> &gt; BC9E172DE1BA5B24EBB4A628177B55985D75751B, which can be found in the
> keys
> &gt; file:
> &gt; https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
> &gt;
> &gt;
> &gt; Checklist for reference,
> &gt; Note that this is not official policy but may help with checking
> releases.
> &gt; Fill in the following:
> &gt; [ ]  Checksums and PGP signatures are valid for Source package.
> &gt; [ ]  Checksums and PGP signatures are valid for Binary package.
> &gt; [ ]  Source code artifacts have correct names matching the current
> release.
> &gt; [ ]  Binary artifacts have correct names matching the current release.
> &gt; [ ]  License and Notice are correct in source package.
> &gt; [ ]  License and Notice are correct in binary package.
> &gt; [ ]  All files have license headers in source package if necessary.
> &gt; [ ]  No compiled archives bundled in source archive.
> &gt; [ ]  Hash and Tag in GitHub repo is matching the current artifacts.
> &gt; [ ]  The code can be built success in the source package.
> &gt; And any other check point is welcomed and please feel free to reply
> to this email, we sincerely hope to your feedback.
> &gt;
> &gt;
> &gt; The vote will be open for at least 72 hours or until necessary number
> of
> &gt; votes are reached.
> &gt; Please vote accordingly:
> &gt;
> &gt;
> &gt; [ ] +1 approve
> &gt; [ ] +0 no opinion
> &gt; [ ] -1 disapprove with the reason
> &gt;
> &gt;
> &gt; Thanks,
> &gt; The Apache RocketMQ Team
> &gt;
> </d...@apache.org>



-- 
Nothing is impossible

Re: [VOTE]Release Apache RocketMQ Client CPP 2.2.0 RC1.

Posted by 金融通 <ji...@mails.ucas.ac.cn>.
+1, 
I checked
-  Checksums and PGP signatures are valid for Source package.
-  Checksums and PGP signatures are valid for Binary package.
-  Hash and Tag in GitHub repo is matching the current artifacts.
-  License and Notice are correct in source package.
-  License and Notice are correct in binary package.



&gt; -----原始邮件-----
&gt; 发件人: ShannonDing <di...@apache.org>
&gt; 发送时间: 2020-04-07 09:44:04 (星期二)
&gt; 收件人: "dev@rocketmq.apache.org" <de...@rocketmq.apache.org>
&gt; 抄送: 
&gt; 主题: [VOTE]Release Apache RocketMQ Client CPP 2.2.0 RC1.
&gt; 
&gt; Hello RocketMQ Community,
&gt; This is the vote for version 2.2.0 of Apache RocketMQ Client CPP.
&gt; This release support TLS mode with OpenSSL for sending messages in sync model and consuming messages by push model and use an separate producer to send trace messages. 
&gt; 
&gt; 
&gt; The artifacts:
&gt; https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/2.2.0-rc1/
&gt; Git tag for the release:
&gt; https://github.com/apache/rocketmq-client-cpp/releases/tag/2.2.0
&gt; Hash for the release tag:
&gt; 6579eb637f81bca29f59f1e8645897a8c12a0871
&gt; Release Notes:
&gt; http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-2.2.0/
&gt; The artifacts have been signed with Key :
&gt; BC9E172DE1BA5B24EBB4A628177B55985D75751B, which can be found in the keys
&gt; file:
&gt; https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
&gt; 
&gt; 
&gt; Checklist for reference,
&gt; Note that this is not official policy but may help with checking releases.
&gt; Fill in the following:
&gt; [ ]  Checksums and PGP signatures are valid for Source package.
&gt; [ ]  Checksums and PGP signatures are valid for Binary package.
&gt; [ ]  Source code artifacts have correct names matching the current release.
&gt; [ ]  Binary artifacts have correct names matching the current release.
&gt; [ ]  License and Notice are correct in source package.
&gt; [ ]  License and Notice are correct in binary package.
&gt; [ ]  All files have license headers in source package if necessary.
&gt; [ ]  No compiled archives bundled in source archive.
&gt; [ ]  Hash and Tag in GitHub repo is matching the current artifacts.
&gt; [ ]  The code can be built success in the source package.
&gt; And any other check point is welcomed and please feel free to reply to this email, we sincerely hope to your feedback.
&gt; 
&gt; 
&gt; The vote will be open for at least 72 hours or until necessary number of
&gt; votes are reached.
&gt; Please vote accordingly:
&gt; 
&gt; 
&gt; [ ] +1 approve
&gt; [ ] +0 no opinion
&gt; [ ] -1 disapprove with the reason
&gt; 
&gt; 
&gt; Thanks,
&gt; The Apache RocketMQ Team
&gt; 
</d...@apache.org>

Re:[VOTE]Release Apache RocketMQ Client CPP 2.2.0 RC1.

Posted by ShannonDing <di...@apache.org>.
+1,
As the release manager, I have checked:
[ 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.
[ OK]  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,
Looking forward to your feedback.
On 04/7/2020 09:44,ShannonDing<di...@apache.org> wrote:
Hello RocketMQ Community,
This is the vote for version 2.2.0 of Apache RocketMQ Client CPP.
This release support TLS mode with OpenSSL for sending messages in sync model and consuming messages by push model and use an separate producer to send trace messages.


The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/2.2.0-rc1/
Git tag for the release:
https://github.com/apache/rocketmq-client-cpp/releases/tag/2.2.0
Hash for the release tag:
6579eb637f81bca29f59f1e8645897a8c12a0871
Release Notes:
http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-2.2.0/
The artifacts have been signed with Key :
BC9E172DE1BA5B24EBB4A628177B55985D75751B, 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: [VOTE]Release Apache RocketMQ Client CPP 2.2.0 RC1.

Posted by liqipeng <wl...@163.com>.
+1, 
I checked
-  Checksums and PGP signatures are valid for Source package.
-  Checksums and PGP signatures are valid for Binary package.
-  License and Notice are correct in source package.
-  No compiled archives bundled in source archive.
-  Hash and Tag in GitHub repo is matching the current artifacts.
-  Source code artifacts have correct names matching the current release.
-  Binary artifacts have correct names matching the current release.


> 在 2020年4月7日,上午9:44,ShannonDing <di...@apache.org> 写道:
> 
> Hello RocketMQ Community,
> This is the vote for version 2.2.0 of Apache RocketMQ Client CPP.
> This release support TLS mode with OpenSSL for sending messages in sync model and consuming messages by push model and use an separate producer to send trace messages. 
> 
> 
> The artifacts:
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/2.2.0-rc1/
> Git tag for the release:
> https://github.com/apache/rocketmq-client-cpp/releases/tag/2.2.0
> Hash for the release tag:
> 6579eb637f81bca29f59f1e8645897a8c12a0871
> Release Notes:
> http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-2.2.0/
> The artifacts have been signed with Key :
> BC9E172DE1BA5B24EBB4A628177B55985D75751B, 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
>