Re:[VOTE] Release Apache RocketMQ Dashboard 2.0.0

[ShannonDing]

+1








At 2024-09-19 20:57:35, "jinrongtong"  wrote:
>Hello RocketMQ Community,
>
>This is the vote for the 2.0.0 release of Apache RocketMQ Dashboard.
>
>The artifacts:
>https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-dashboard/2.0.0-rc1/
>
>
>The staging repo:
>https://repository.apache.org/content/repositories/orgapacherocketmq-1332
>
>
>Git tag for the release:
>https://github.com/apache/rocketmq-dashboard/releases/tag/rocketmq-dashboard-2.0.0
>
>
>Hash for the release tag:
>f5c09ac287249cf2a2a0b0c95d7fbca8d8a59a38
>
>
>Release Notes:
>https://rocketmq.apache.org/release-notes/2024/09/18/release-notes-rocketmq-dashboard-2.0.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

Re:Re:[VOTE] Release Apache RocketMQ C# Client 5.2.0 RC1

[ShannonDing]

+1








At 2024-09-25 17:39:59, "jinrongtong"  wrote:
>+1， I checked [OK]  Hash and Tag in GitHub repo is matching the current 
>artifacts.[OK]  verify the asc(PGP sign),SHA512[OK]  Release note is 
>ok
>At 2024-09-25 11:28:31, "Jack Tsai"  wrote:
>>Hello RocketMQ Community,
>>
>>This is the vote for Apache RocketMQ C# Client 5.2.0 RC1.
>>
>>This release is to improve some features and issues for Apache RocketMQ C#
>>Client, including Push Consumer and namespace support, along with other
>>important features.
>>
>>The artifacts:
>>https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-clients/rocketmq-client-csharp/5.2.0-rc1/
>>
>>The staging repo:
>>https://www.nuget.org/packages/RocketMQ.Client/5.2.0-rc1
>>
>>Git tag for the release:
>>https://github.com/apache/rocketmq-clients/releases/tag/csharp-5.2.0-rc1
>>
>>
>>Hash for the release tag:
>>51fcf33e9dd8b25b4e8669124b0171a58ab7ebbd
>>
>>Release Notes:
>>https://rocketmq.apache.org/release-notes/2024/09/25/release-notes-rocketmq-csharp-client-5.2.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:
>>[ ] check LICENSE, should be Apache V2
>>[ ] check NOTICE, should have a notice for third-party dependency if
>>necessary
>>[ ] extract the zip and check if the source version is correct
>>[ ] verify the asc(PGP sign),SHA512
>>[ ] build the source, start nameserver and broker according to the
>>quick-start
>>[ ] run clusterList command to see if the version is correct
>>
>>The vote will be open for at least 72 hours or until the 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 Spring 2.3.1 RC1

[ShannonDing]

+1







At 2024-07-22 10:10:04, "jinrongtong"  wrote:

Hello RocketMQ Community,

This is the vote for the 2.3.1 release of Apache RocketMQ-Spring.



The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-spring/2.3.1-rc1/


The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1331


Git tag for the release:
https://github.com/apache/rocketmq-spring/releases/tag/rocketmq-spring-all-2.3.1


Hash for the release tag:
63e8711677d90fb188e68558edb02bc642e75bf6


Release Notes:
https://rocketmq.apache.org/zh/release-notes/2024/07/19/release-notes-rocketmq-spring-2.3.1


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

Re:[VOTE][RIP-70]Optimizing Lock Mechanisms

[ShannonDing]

+1


At 2024-07-14 08:42:36, "王怀远" <3424672...@qq.com.INVALID> wrote:
>Hi, RocketMQ Community,
>
>
>
>
>As discussed in the previous email, we launched a new RIP 70 to Optimizing 
>Lock Mechanisms. Now the shepherds @RongtongJin is willing to support the RIP, 
>so I think it is time to start an email thread to enter the voting process.
>
>
>
>
>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
>
>
>
>
>Best Regards!
>HuaiYuan Wang
>
>
>
>
>Proposal:  https://shimo.im/docs/473QM8m8ByCn6l3w
>
>
>
>
>
>
>left
>3424672...@qq.com
>
>
>
>王怀远
>3424672...@qq.com
>
>
>
> 

Re:[VOTE]: Release Apache RocketMQ 5.3.0

[ShannonDing]

+1


At 2024-07-10 20:02:37, "zhimin li"  wrote:
>Hello RocketMQ Community,
>This is the vote for 5.3.0 of Apache RocketMQ. This release contains
>some important bug fix and improvement.
>
>*The artifacts:*
>https://dist.apache.org/repos/dist/dev/rocketmq/5.3.0-rc1/
>
>*The staging repo:*
>https://repository.apache.org/content/repositories/orgapacherocketmq-1329/org/apache/rocketmq/
>
>*Git tag for the release:*
>https://github.com/apache/rocketmq/tree/rocketmq-all-5.3.0
>
>*Hash for the release tag:*
>7ee50ec32e10265c45e00df5971dd78b9598ff6e
>
>*Release Notes:*
>https://github.com/apache/rocketmq-site/pull/667/files#diff-a836b0b4687b951c221f114b684d737f66f3c7acc486c54c9733d1f5c8f39a3d
>
>The artifacts have been signed with
>Key 09D58134D2DA90B296ABCB77D5C871BAC9D394D2 which can be found in the
>keys file:
>https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
>
>The vote will be open for at least 72 hours or until the 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:Re: [VOTE] Release Apache RocketMQ Exporter 0.0.2

[ShannonDing]

+1




At 2024-02-20 10:07:57, "heng du"  wrote:

+1

I checked:
check LICENSE, should be Apache V2
check NOTICE, should have a notice for third-party dependency if necessary
Hash and Tag in GitHub repo is matching the current artifacts




jinrongtong  于2024年2月13日周二 18:10写道：

+1, I checked[OK]  Checksums and PGP signatures are valid for Source 
package.[OK]  Hash and Tag in GitHub repo is matching the current 
artifacts.In addition, it would be better to update the copyright year in 
the notice file during the next release.
At 2024-02-13 17:53:29, "Gaoyang Cai"  wrote:
>Hello RocketMQ Community,
>
>This is the vote for 0.0.2 RC1 of Apache RocketMQ Exporter.
>
>This is the first formal release for Apache RocketMQ Exporter. All changes 
>since supporting Apache RocketMQ 4.x are included, as well as those making it 
>compatible to Apache RocketMQ 5.x. The group id of maven has been modified 
>according to guidelines of ASF.
>
>
>The artifacts:
>https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-exporter/0.0.2-rc1/
>
>The staging repo:
>https://repository.apache.org/content/repositories/orgapacherocketmq-1304/
>
>Git tag and release notes for the release:
>https://github.com/apache/rocketmq-exporter/releases/tag/rocketmq-exporter-0.0.2
>
>Hash for the release tag:
>696f346f5a18396fe8074611981e77338a16af41
>
>The artifacts have been signed with Key:
>D45CD805DE178E32B8427AD5E14A98593C6E6037 , 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:
>[ ]  check LICENSE, should be Apache V2
>[ ]  check NOTICE, should have a notice for third-party dependency if necessary
>[ ]  extract the zip and check if the source version is correct
>[ ]  verify the asc(PGP sign),SHA512 and docker image is correct
>[ ]  build the source, start exporter according to the quick-start
>
>The vote will be open for at least 72 hours or until the 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 Spring 2.3.0 RC1

[ShannonDing]

+1

At 2024-02-20 14:16:45, "jinrongtong"  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

Re:[VOTE] Release Apache RocketMQ 4.9.8 RC2

[ShannonDing]

+1


At 2024-02-23 10:31:35, "jinrongtong"  wrote:
>Hello RocketMQ Community,
>
>This is the vote for 4.9.8 RC2 of Apache RocketMQ.
>
>This release fixes some bugs to enhance stability.
>
>The artifacts:
>https://dist.apache.org/repos/dist/dev/rocketmq/4.9.8-rc2/
>
>The staging repo:
>https://repository.apache.org/content/repositories/orgapacherocketmq-1314
>
>Git tag for the release:
>https://github.com/apache/rocketmq/tree/release-4.9.8
>
>Hash for the release tag:
>2bdd53ef6694ffa19fd00db0b887e4895444f63e
>
>Release Notes:
>https://rocketmq.apache.org/zh/release-notes/2024/01/29/4.9.8/
>
>
>
>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 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.
>[]  Start nameserver and broker according to the quick-start
>[]  Run clusterList command to see if the version is correct
>
>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 5.2.0 RC1

[ShannonDing]

+1





At 2024-02-13 18:17:54, "jinrongtong"  wrote:
>Hello RocketMQ Community,
>
>This is the vote for 5.2.0 RC1 of Apache RocketMQ.
>
>This release includes fixes for many issues, enhancements to stability, and 
>also introduces some significant features, including the million-level queue 
>and the implementation of the jraft controller.
>
>The artifacts:
>https://dist.apache.org/repos/dist/dev/rocketmq/5.2.0-rc1/
>
>
>The staging repo:
>https://repository.apache.org/content/repositories/orgapacherocketmq-1303/
>
>
>Git tag for the release:
>https://github.com/apache/rocketmq/releases/tag/rocketmq-all-5.2.0
>
>
>Hash for the release tag:
>281a7b32f002019525cfa4dd4a4b983b653f070d
>
>
>Release Notes:
>https://rocketmq.apache.org/zh/release-notes/2024/01/30/5.2.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:
>[ ]  check LICENSE, should be Apache V2
>[ ]  check NOTICE, should have a notice for third-party dependency if necessary
>[ ]  extract the zip and check if the source version is correct
>[ ]  verify the asc(PGP sign),SHA512
>[ ]  build the source, start nameserver and broker according to the quick-start
>[ ]  run clusterList command to see if the version is correct
>
>
>The vote will be open for at least 72 hours or until the 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 4.9.8 RC1

[ShannonDing]

+1





At 2024-02-13 18:17:38, "jinrongtong"  wrote:
>Hello RocketMQ Community,
>
>This is the vote for 4.9.8 of Apache RocketMQ.
>
>This release fixes some bugs to enhance stability.
>
>The artifacts:
>https://dist.apache.org/repos/dist/dev/rocketmq/4.9.8-rc1/
>
>The staging repo:
>https://repository.apache.org/content/repositories/orgapacherocketmq-1309
>
>Git tag for the release:
>https://github.com/apache/rocketmq/tree/release-4.9.8
>
>Hash for the release tag:
>8b287928fb4c8c565282c019ef668c43e6eb3289
>
>Release Notes:
>https://rocketmq.apache.org/zh/release-notes/2024/01/29/4.9.8/
>
>
>
>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 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.
>[]  Start nameserver and broker according to the quick-start
>[]  Run clusterList command to see if the version is correct
>
>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:Re:Re: [VOTE][RIP-69] Support MQTT 5.0 In RocketMQ-MQTT

[ShannonDing]

+1


在 2024-01-10 18:46:50，"jinrongtong"  写道：
>+1
>在 2024-01-10 11:37:52，"Ping Wang"  写道：
>>+1
>>
>>Dongyuan Pan  于2024年1月8日周一 09:55写道：
>>
>>> Hi RocketMQ Community,
>>>
>>> Since the time for this RIP discussion has already passed, I’d like to
>>> start the vote for it. The proposal is provided below:
>>>
>>> Google Doc version:
>>>
>>> https://docs.google.com/document/d/1S2KtV9JInH61nJqkETengFRnHG_1KV4WZMnnoS_1KsM/edit?usp=sharing
>>>
>>>
>>> Shimo version:
>>> https://shimo.im/docs/25q5XEolX4tep63D/ 「[RIP-69] Support MQTT 5.0 In
>>> RocketMQ-MQTT」
>>>
>>>
>>> The vote will be open for at least 72 hours or until the necessary
>>> number of votes are reached.
>>>
>>> Please vote accordingly:
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove with the reason
>>>

Re:[VOTE] Release Apache RocketMQ 5.1.3 RC1

[ShannonDing]

+1

At 2023-06-25 11:04:06, "jinrongtong"  wrote:

Hello RocketMQ Community,

This is the vote for 5.1.3 of Apache RocketMQ.

This release fixes some bugs to enhance stability.

The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/5.1.3-rc1/

The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1232

Git tag for the release:
https://github.com/apache/rocketmq/tree/release-5.1.3

Hash for the release tag:
f7425f52f9f1d1132ecdea053bdc57a583a5d9e3




Release Notes:
https://rocketmq.apache.org/zh/release-notes/2023/06/24/5.1.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 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.
[]  Start nameserver and broker according to the quick-start
[]  Run clusterList command to see if the version is correct

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 4.9.7 RC1

[ShannonDing]

+1.


At 2023-06-13 15:02:10, "jinrongtong"  wrote:
>Hello RocketMQ Community,
>
>This is the vote for 4.9.7 of Apache RocketMQ.
>
>This release fixes some bugs to enhance stability.
>
>The artifacts:
>https://dist.apache.org/repos/dist/dev/rocketmq/4.9.7-rc1/
>
>The staging repo:
>https://repository.apache.org/content/repositories/orgapacherocketmq-1230
>
>Git tag for the release:
>https://github.com/apache/rocketmq/tree/release-4.9.7
>
>Hash for the release tag:
>5eb2e4ca0e18e80b91a38cf6f31429966d349e41
>
>
>
>
>Release Notes:
>https://rocketmq.apache.org/zh/release-notes/2023/06/12/4.9.7/
>
>
>
>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 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.
>[]  Start nameserver and broker according to the quick-start
>[]  Run clusterList command to see if the version is correct
>
>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 5.1.2 RC1

[ShannonDing]

+1




At 2023-06-13 15:01:09, "jinrongtong"  wrote:

Hello RocketMQ Community,

This is the vote for 5.1.2 of Apache RocketMQ.

This release fixes some bugs to enhance stability.

The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/5.1.2-rc1/

The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1229

Git tag for the release:
https://github.com/apache/rocketmq/tree/release-5.1.2

Hash for the release tag:
749967baa82bafb155353351154b5c6ace095574




Release Notes:
https://rocketmq.apache.org/zh/release-notes/2023/06/12/5.1.2/



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 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.
[]  Start nameserver and broker according to the quick-start
[]  Run clusterList command to see if the version is correct

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 4.9.6 RC1

[ShannonDing]

+1



At 2023-05-18 13:34:25, "jinrongtong"  wrote:

Hello RocketMQ Community,

This is the vote for 4.9.6 of Apache RocketMQ.

This release fixes some bugs to enhance stability.

The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/4.9.6-rc1/

The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1194

Git tag for the release:
https://github.com/apache/rocketmq/tree/release-4.9.6

Hash for the release tag:
db4ba459bec9392ac37647ff1a4d24d30466814d




Release Notes:
https://rocketmq.apache.org/zh/release-notes/2023/05/18/4.9.6/



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 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.
[]  Start nameserver and broker according to the quick-start
[]  Run clusterList command to see if the version is correct

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 5.1.1 RC1

[ShannonDing]

+1， 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.

At 2023-05-16 08:26:38, "jinrongtong"  wrote:

Hello RocketMQ Community,

This is the vote for 5.1.1 of Apache RocketMQ.

This release fixes some bugs to enhance stability.

The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/5.1.1-rc1/

The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1193

Git tag for the release:
https://github.com/apache/rocketmq/tree/release-5.1.1

Hash for the release tag:
e244ebb99a1ba5e5dac174c699da8b83a273e7fd




Release Notes:
https://rocketmq.apache.org/zh/release-notes/2023/05/15/5.1.1/



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 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.
[]  Start nameserver and broker according to the quick-start
[]  Run clusterList command to see if the version is correct

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:Re: Re: [VOTE][RIP-64] Heartbeat Optimization

[ShannonDing]

+1


在 2023-04-28 11:50:13，"fuyou"  写道：
>+1
>
>jinrongtong  于2023年4月28日周五 09:27写道：
>
>> +1
>> 在 2023-04-27 18:57:20，"Ji Juntao" <3160102...@zju.edu.cn> 写道：
>> >+1
>> >
>> >
>> >> -原始邮件-
>> >> 发件人: "2017赵科" <464473...@qq.com.INVALID>
>> >> 发送时间: 2023-04-27 10:39:36 (星期四)
>> >> 收件人: dev 
>> >> 抄送:
>> >> 主题: [VOTE][RIP-64] Heartbeat Optimization
>> >>
>> >> Hi, RocketMQ Community,
>> >>
>> >>
>> >> As discussed in the previous email, we launched a new
>> RIP[RIP-64]Heartbeat Optimization to support this feature. Now the 
>> >>
>> >>
>> >> i...@foxmail.com is willing to support the RIP, so I think it is time
>> to start an email thread to enter the voting process.
>> >>
>> >>
>> >> 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
>> >>
>> >>
>> >> Best Regards!
>> >> drizzle.zk
>> >>
>> >>
>> >>
>> >>
>> >> links:
>> >> Google Doc:
>> https://docs.google.com/document/d/174p0N7yDX0p_jvaujwHGFsZ410FKbq3vqGT1RUUyV1c/edit?usp=sharing
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> 2017赵科
>> >> 464473...@qq.com
>> >>
>> >>
>> >>
>> >>  
>>
>
>
>-- 
>   =
>
>  fuyou001
>Best Regards

Re:[VOTE]Release Apache RocketMQ 4.9.5 RC1

[ShannonDing]

+1

At 2023-03-27 18:51:29, "jinrongtong"  wrote:

Hello RocketMQ Community,

This is the vote for 4.9.5 of Apache RocketMQ.

This release fixes some bugs and supports bname in protocol for 4.9.5 client 
accessing proxy.

The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/4.9.5-rc1/

The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1172

Git tag for the release:
https://github.com/apache/rocketmq/tree/release-4.9.5

Hash for the release tag:
66b7e6f5f1d383a68082a2d5a9609f5165532841
 


Release Notes:
https://rocketmq.apache.org/zh/release-notes/2023/03/26/4.9.5/

 
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 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.
[]  Start nameserver and broker according to the quick-start
[]  Run clusterList command to see if the version is correct

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][RIP-62]Coldreadcontrol

[ShannonDing]

+1

At 2023-03-07 14:55:05, "2017赵科" <464473...@qq.com.INVALID> wrote:
>Hi, RocketMQ Community,
>
>
>As discussed in the previous email, we launched a new RIP[RIP-62] Cold read 
>control to support this feature. Now the i...@foxmail.com
> is willing to support the RIP, so I think it is time to start an email 
>thread to enter the voting process.
>
>
>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
>
>
>Best Regards!
>drizzle.zk
>
>
>
>
>links:
>Google 
>Doc: https://docs.google.com/document/d/1P8JPX5b9CwYMlaFi_UBxqwxFoIiOXWuAEjV4yWdfFUw/edit?usp=sharing
>
>
>
>
>
>
>
>
>2017赵科
>464473...@qq.com
>
>
>
> 

Re:[VOTE]Release Apache RocketMQ Spring 2.2.3 RC1

[ShannonDing]

+1.




At 2023-02-06 13:36:43, "jinrongtong"  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

Re:[VOTE] Release RocketMQ Streams 1.1.0

[ShannonDing]

+1


At 2023-01-06 14:08:57, "nize"  wrote:
>This is the discussion for the release of Rocketmq Streams 1.1.0 version.
>
>RocketMQ Streams is a lightweight stream processing framework, application
>gains the stream processing ability by depending on RocketMQ Streams as an
>SDK.
>
>
>The artifacts:
>
>https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-streams/1.1.0/
>
>
>The staging repo:
>
>https://repository.apache.org/content/repositories/orgapacherocketmq-1132/
>
>
>Git tag for the release:
>
>https://github.com/apache/rocketmq-streams/releases/tag/rocketmq-streams-all-1.1.0
>
>
>Hash for the release tag:
>
>51402a36218f530ee05e21e9a1abce23ea06169b
>
>
>Relate Notes:
>
>https://github.com/apache/rocketmq-streams/releases/tag/rocketmq-streams-all-1.1.0
>
>
>
>The artifacts have been signed with Key :
>
>C15E0A9888919CC8A2F7EBB0268C587BB6345D14,which can be found in the keys
>
>file: https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
>
>
>
>Fill in the following:
>
>[ ]  check LICENSE, should be Apache V2
>
>[ ]  check NOTICE, should have a notice for third-party dependency if
>necessary
>
>[ ]  extract the zip and check if the source version is correct
>
>[ ]  verify the asc(PGP sign),SHA512
>
>[ ] build the source, start rocketmq schema registry server according to
>the quick-start
>
>
>The vote will be open for at least 72 hours or until the 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][RIP-59] Support DLedger Controller Snapshot

[ShannonDing]

+1


At 2022-12-20 17:54:41, "Jack Tsai"  wrote:
>Hi RocketMQ Community,
>
>Since the time for this RIP discussion has already passed, I’d like to start 
>the vote for it. The proposal is provided below:
>
>Google Doc version:
>https://docs.google.com/document/d/1jiKtv5WRDqlgZLGYK0oHuZww1r7KKrnTdRGf_eDIQy8/edit?usp=sharing
>
>Shimo version:
>https://shimo.im/docs/WlArzngm9JhzY0A2
>
>
>The vote will be open for at least 72 hours or until the necessary number of 
>votes are reached.
>
>Please vote accordingly:
>[ ] +1 approve
>[ ] +0 no opinion
>[ ] -1 disapprove with the reason
>
>Best regards,
>Jack (Tsung-Han) Tsai

Re:[VOTE][RIP-58]RocketMQ Streams improvement

[ShannonDing]

+1


At 2022-12-05 17:40:10, "nize"  wrote:
>Hi, RocketMQ Community,
>
>As discussed in the previous email, we launched a new RIP to  start it. Now
>the shepherds @ShannonDing <https://github.com/ShannonDing> and @RongtongJin
><https://github.com/RongtongJin>
> are willing to support the RIP, so I think it is time to start an email
>thread to enter the voting process.
>
>Design:
>https://shimo.im/docs/25q5Mw5bpysQN2qD
>
>Chinese version:
>https://shimo.im/docs/m8AZVd71ojHDZpAb
>
>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
>
>Best Regards!

Re:[VOTE]: Release Apache RocketMQ Schema Registry 0.1.0

[ShannonDing]

+1


At 2022-10-24 17:24:21, "nize"  wrote:
>Hello RocketMQ Community,
>
>This is the vote for  0.1.0  of Apache RocketMQ Schema Registry.
>
>RocketMQ Schema Registry is a Topic Schema's management center. It provides
>a RESTful interface for register, delete, update, get and reference schema
>to subject(RocketMQ Topic). By associating Schema with subject, the New
>RocketMQ client can send structured data directly. Users no longer need to
>care about the details of serialization and deserialization.
>
>The artifacts:
>https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-schema-registry/
>
>The staging repo:
>https://repository.apache.org/content/repositories/orgapacherocketmq-1127/
>
>Git tag for the release:
>https://github.com/apache/rocketmq-schema-registry/releases/tag/rocketmq-schema-registry-all-0.1.0
>
>Hash for the release tag:
>c57330155e05559a1e2f56aa3a2ed62750c339da
>
>Relate Notes:
>https://github.com/apache/rocketmq-schema-registry/releases/tag/rocketmq-schema-registry-all-0.1.0
>
>
>The artifacts have been signed with Key :
>
>C15E0A9888919CC8A2F7EBB0268C587BB6345D14,which can be found in the keys
>
>file: https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
>
>Fill in the following:
>
>[ ]  check LICENSE, should be Apache V2
>
>[ ]  check NOTICE, should have a notice for third-party dependency if
>necessary
>
>[ ]  extract the zip and check if the source version is correct
>
>[ ]  verify the asc(PGP sign),SHA512
>
>[ ] build the source, start rocketmq schema registry server according to
>the quick-start
>
>
>The vote will be open for at least 72 hours or until the 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 Schema Registry 0.1.0

[ShannonDing]

+1

At 2022-10-18 11:41:32, "nize"  wrote:
>Hello RocketMQ Community,
>
>This is the vote for  0.1.0  of Apache RocketMQ Schema Registry.
>
>RocketMQ Schema Registry is a Topic Schema's management center. It provides
>a RESTful interface for register, delete, update, get and reference schema
>to subject(RocketMQ Topic). By associating Schema with subject, the New
>RocketMQ client can send structured data directly. User no longer need to
>care about the details of serialization and deserialization.
>
>The artifacts:
>https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-schema-registry/
>
>The staging repo:
>https://repository.apache.org/content/repositories/orgapacherocketmq-1109/
>
>Git tag for the release:
>https://github.com/apache/rocketmq-schema-registry/releases/tag/rocketmq-schema-registry-all-0.1.0
>
>Hash for the release tag:
>84184bbecbc13ed47ca6d46976430fa8aa08fb9c
>
>Relate Notes:
>https://github.com/apache/rocketmq-schema-registry/releases/tag/rocketmq-schema-registry-all-0.1.0
>
>
>The artifacts have been signed with Key :
>
>C15E0A9888919CC8A2F7EBB0268C587BB6345D14,which can be found in the keys
>
>file: https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
>
>Fill in the following:
>
>[ ]  check LICENSE, should be Apache V2
>
>[ ]  check NOTICE, should have a notice for third-party dependency if
>necessary
>
>[ ]  extract the zip and check if the source version is correct
>
>[ ]  verify the asc(PGP sign),SHA512
>
>[ ] build the source, start rocketmq schema registry server according to
>the quick-start
>
>
>The vote will be open for at least 72 hours or until the necessary number
>of votes are reached.
>
>Please vote accordingly:
>
>
>
>
>[ ] +1 approve
>
>[ ] +0 no opinion
>
>[ ] -1 disapprove with the reason
>
>
>
>
>Thanks
>
>The Apache RocketMQ Team

[ANNOUNCE]New Committers of Apache RocketMQ: Yang Tianyang(apache id: ayanamist)

[ShannonDing]

Hi Apache RocketMQ Community,




The Project Management Committee (PMC) for Apache RocketMQ has invited

Yang Tianyang(apache id: ayanamist),

to become a committer, and we are pleased to announce that he has accepted. 




Congrats, guy :-)




Best Wishes,

ShannonDing

Re:Re:Re:Re:[RESTART][VOTE]Release Apache RocketMQ 5.0.0 RC2

[ShannonDing]

+1，checked：
[OK]  check LICENSE, should be Apache V2
[OK]  check NOTICE, should have a notice for third-party dependency if necessary
[OK]  extract the zip and check if the source version is correct
[OK]  verify the asc(PGP sign),SHA512

At 2022-09-20 14:25:42, "Gaoyang Cai"  wrote:
>
>+1 (Non-binding)
>
>
>I checked: 
>
>[OK]  check LICENSE, should be Apache V2
>
>[OK]  check NOTICE, should have a notice for third-party dependency if 
>necessary
>
>[OK]  extract the zip and check if the source version is correct
>
>[OK]  verify the asc(PGP sign),SHA512
>
>[OK]  build the source, start nameserver and broker according to the 
>quick-start
>
>[OK]  run clusterList command to see if the version is correct
>
>
>
>
>
>
>At 2022-09-20 09:09:07, "jinrongtong"  wrote:
>>+1, I checked[OK]  extract the zip and check if the source version 
>>is correct[OK]  verify the asc(PGP sign),SHA512[OK]  
>>maven jar in nexus repo is right
>>At 2022-09-19 19:39:25, "hill"  wrote:
>>>Git tag for the release should be updated to
>>>
>>>
>>>
>>>f3e113cb1f98ced8327e7c97bfb5a623950339ef
>>>
>>>
>>>
>>>
>>>At 2022-09-19 13:27:57, "hill"  wrote:
>>>
>>>Hello RocketMQ Community,
>>>
>>>
>>>
>>>
>>>This is the vote for 5.0.0 RC2 of Apache RocketMQ.
>>>
>>>This release is to improve some features and issues for apache rocketmq,such 
>>>as grpc proxy ,batch message,  static topic ，new ha architecture ，fix some 
>>>bugs and issues and so on.
>>>
>>>
>>>
>>>
>>>The artifacts:
>>>
>>>https://dist.apache.org/repos/dist/dev/rocketmq/5.0.0-rc2/
>>>
>>>
>>>
>>>
>>>The staging repo:
>>>
>>>https://repository.apache.org/content/repositories/orgapacherocketmq-1100/
>>>
>>>
>>>
>>>
>>>Git tag for the release:
>>>
>>>https://github.com/apache/rocketmq/releases/tag/rocketmq-all-5.0.0
>>>
>>>
>>>
>>>
>>>Hash for the release tag:
>>>
>>>3f7b0fd17be14f15bd12d19afcbea26fa9ee5560
>>>
>>>f3e113cb1f98ced8327e7c97bfb5a623950339ef
>>>
>>>
>>>
>>>
>>>Release Notes:
>>>
>>>https://rocketmq.apache.org/third-blog/2022/09/09/5.0.0/
>>>
>>>
>>>
>>>
>>>The artifacts have been signed with Key :
>>>
>>>D011F2A8C9474A34099477A5C99B3EAC6B119386, 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:
>>>
>>>[ ]  check LICENSE, should be Apache V2
>>>
>>>[ ]  check NOTICE, should have a notice for third-party dependency if 
>>>necessary
>>>
>>>[ ]  extract the zip and check if the source version is correct
>>>
>>>[ ]  verify the asc(PGP sign),SHA512
>>>
>>>[ ]  build the source, start nameserver and broker according to the 
>>>quick-start
>>>
>>>[ ]  run clusterList command to see if the version is correct
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>The vote will be open for at least 72 hours or until the 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 Operator 0.3.0

[ShannonDing]

+1


At 2022-09-13 11:25:00, "Gaoyang Cai"  wrote:
>Hello RocketMQ Community,
>
>
>This is the vote for 0.3.0 release of Apache RocketMQ Operator.
>
>In this release, accessing Apache RocketMQ from outside the Kubernetes cluster 
>is available, the addresses of Name Servers can be set automatically, memory 
>limit in container is sensible so that calculation of JVM parameters is more 
>accurate. The version of operator-sdk has been updated to 1.16. Also, the 
>docker repository for rocketmq-operator has been moved to an official 
>repository under Apache.
>
>
>
>Docker image for Apache RocketMQ Operator: apache/rocketmq-operator:0.3.0
>
>Docker image repo: 
>https://hub.docker.com/layers/apache/rocketmq-operator/0.3.0/images/sha256-7fe24ce7cbac5fca29b6d0b2412e388de084b19ce1ac189734661b94037d49c7?context=explore
>
>
>Git tag and release notes for the release:
>https://github.com/apache/rocketmq-operator/releases/tag/0.3.0
>
>
>Hash for the release tag:
>23fb2eb094470d60b964aef8539f4a4ae3a752c6
>
>
>Checklist for reference:
>Note that this is not an official policy but may help with checking releases.
>
>Fill in the following:
>[ ]  check LICENSE, should be Apache V2
>[ ]  check NOTICE, should have a notice for third-party dependency if
>necessary
>[ ]  verify the hash for release tag and docker image is correct
>[ ]  deploy Apache RocketMQ by Operator
>
>
>
>The vote will be open for at least 72 hours or until the necessary number of 
>votes are reached.
>
>Please vote accordingly:
>
>[ ] +1 approve
>
>[ ] +0 no opinion
>
>[ ] -1 disapprove with the reason
>
>
>
>
>Thanks,
>
>The Apache RocketMQ Team

[ANNOUNCE]New Committers of Apache RocketMQ: Sun Xiaojian(apache id: sunxiaojian)

[ShannonDing]

Hi Apache RocketMQ Community,




The Project Management Committee (PMC) for Apache RocketMQ has invited

Sun Xiaojian(apache id: sunxiaojian),

to become a committer, and we are pleased to announce that he has accepted. 




Congrats, guy :-)




Best Wishes,

ShannonDing

[ANNOUNCE] Release Apache RocketMQ Client Native Go 2.1.1

[ShannonDing]

Hello RocketMQ Community,




The Apache RocketMQ team would like to announce the release of Apache RocketMQ 
Client Native Go 2.1.1.

The main goal of this release is to improve stability, usability, and fix bugs 
and  implement some new features mainly including request-reply mode, consuming 
messages from slave node and supporting IPv6 and so on. 

The release artifacts can be downloaded here:

https://mirrors.tuna.tsinghua.edu.cn/apache/rocketmq/rocketmq-client-go/2.1.1/rocketmq-client-go-2.1.1-source-release.tar.gz




The release notes can be found here:

http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-go-2.1.1/




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




Thanks,

The Apache RocketMQ Team

[RESULT][VOTE]Release Apache RocketMQ Client Go Native 2.1.0.

[ShannonDing]

Hello RocketMQ Community,




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




*Binding votes +1s:*




Du Heng(duhengfore...@apache.org)

Jin Rongtong(jinrongt...@apache.org)

ShannonDing(ding...@apache.org)

yukong(yuk...@apache.org)




*Non-binding votes +1s:*

zongtan...@apache.org

dongyuanp...@gmail.com

fu_jian_z...@qq.com







The release will be published soon.




Thanks,

The Apache RocketMQ Team

Re:​[VOTE]Release Apache RocketMQ Client Go Native 2.1.1.

[ShannonDing]

+1, as RM of this 2.1.1 version, I has checked all issues in list.

At 2022-07-25 21:15:21, "ShannonDing"  wrote:
>Hello RocketMQ Community,
>
>
>
>This is the vote for version 2.1.1 of Apache RocketMQ Client Go Native.
>
>The main goal of this release is to improve stability, usability, and fix bugs 
>and  implement some new features mainly including request-reply mode, 
>consuming messages from slave node and supporting IPv6 and so on. 
>
>
>
>The artifacts:
>
>https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-go/2.1.1-rc3/
>
>Git tag for the release:
>
>https://github.com/apache/rocketmq-client-go/releases/tag/v2.1.1
>
>Hash for the release tag:
>
>129701aef56b3bf215b230ed9285ccb17dc18fe9
>
>Release Notes:
>
>http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-go-2.1.1/
>
>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.
>
>[ ]  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 is matching the current artifacts.
>
>As we don’t release binary package for Apache RocketMQ Go SDK, the binary 
>package checklist should not be followed.
>
>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

​[VOTE]Release Apache RocketMQ Client Go Native 2.1.1.

[ShannonDing]

Hello RocketMQ Community,



This is the vote for version 2.1.1 of Apache RocketMQ Client Go Native.

The main goal of this release is to improve stability, usability, and fix bugs 
and  implement some new features mainly including request-reply mode, consuming 
messages from slave node and supporting IPv6 and so on. 



The artifacts:

https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-go/2.1.1-rc3/

Git tag for the release:

https://github.com/apache/rocketmq-client-go/releases/tag/v2.1.1

Hash for the release tag:

129701aef56b3bf215b230ed9285ccb17dc18fe9

Release Notes:

http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-go-2.1.1/

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.

[ ]  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 is matching the current artifacts.

As we don’t release binary package for Apache RocketMQ Go SDK, the binary 
package checklist should not be followed.

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:Re: [DISCUSS]Release Apache rocketmq-client-go 2.1.1

[ShannonDing]

Great, processing...


At 2022-07-21 18:59:58, "cserwen"  wrote:
>I have two PRs here, welcome to review.
>
>1. https://github.com/apache/rocketmq-client-go/pull/844 
><https://github.com/apache/rocketmq-client-go/pull/844>
>2. https://github.com/apache/rocketmq-client-go/pull/849 
><https://github.com/apache/rocketmq-client-go/pull/849>
>
>
>> 2022年7月20日 09:51，ShannonDing  写道：
>> 
>> 
>> 
>> 
>> Hello RocketMQ Community,
>> 
>> 
>> 
>> 
>> It has been a long time since the last release. During this period, the 
>> project has imported many new features, solved many issues, and made many 
>> optimizations.
>> 
>> So,
>> 
>> Apache RocketMQ team is about to release Apache rocketmq-client-go 2.1.1 and 
>>  we will stop merge PR soon.
>> 
>> If your PR has not been merged and needs further attention, please reply to 
>> this email and we will review it as soon as possible.
>> 
>> 
>> 
>> 
>> Best Regards,
>> 
>> Apache RocketMQ Team.
>

[DISCUSS]Release Apache rocketmq-client-go 2.1.1

[ShannonDing]

Hello RocketMQ Community,




It has been a long time since the last release. During this period, the project 
has imported many new features, solved many issues, and made many optimizations.

So,

Apache RocketMQ team is about to release Apache rocketmq-client-go 2.1.1 and  
we will stop merge PR soon.

 If your PR has not been merged and needs further attention, please reply to 
this email and we will review it as soon as possible.




Best Regards,

Apache RocketMQ Team.

Re:[VOTE][RIP-45]RocketMQ Replicator 2.0

[ShannonDing]

+1





At 2022-07-12 14:31:48, "zhibo li"  wrote:
>Hi, RocketMQ Community,
>
>
>As discussed in the previous email, we launched a new RIP 45 to enhance
>RocketMQ Replicator. Now the shepherds @duhenglucky and @dongeforever are
>willing to support the RIP, so I think it is time to start an email thread
>to enter the voting process.
>
>
>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
>
>
>
>
>
>Best Regards!
>
>Lizhibo
>
>
>
>links:
>
>English proposal:
>https://docs.google.com/document/d/1_gd3ijNW38cHQTeI_iOUX9hg4n_RVGQDLnZxLMJr0lg/edit?usp=sharing
>
>
>Chinese proposal:
>https://shimo.im/file-invite/3EMTZwcWNFh8NW4Vgj4dKtlmGJXK6/

Re:[VOTE] The code of 5.0.0-beta merge into develop branch

[ShannonDing]

+1,

At 2022-07-12 10:18:43, "jinrongtong"  wrote:
>Hi, RocketMQ Community, 
>
>As discussed in the previous email, we want to merge the code of the 5.0-beta 
>into develop branch. We also create a new branch 4.9.x to fix bugs in the 
>4.9.4 LTS version.
>So I start this email thread to enter the voting process for the previous 
>discussion.
>
>
>Note: after the 5.0.0-beta code is merged into develop branch, some large pull 
>requests that have not been merged may have code conflicts, which need to be 
>resolved by yourself. 
>
>
>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
>
>
>Best Regards!
>Rongtong Jin

Re:[VOTE][RIP-44]Support DLedger Controller

[ShannonDing]

+1


At 2022-06-27 11:32:15, "jinrongtong"  wrote:
>Hi, RocketMQ Community, 
>
>As discussed in the previous email, we launched a new RIP 44 to support 
>dledger controller. Now the shepherds @duhenglucky and @dongeforever are 
>willing to support the RIP, so I think it is time to start an email thread to 
>enter the voting process.
>
>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
>
>
>
>
>Best Regards!
>Rongtong Jin
>
>
>links: 
>Discuss email: https://lists.apache.org/thread/bvykv62y4ytqrox5892mgyr1qvc7cngb
>English proposal: 
>https://docs.google.com/document/d/1tSJkor_3Js4NBaVA0UENGyM8Mh0SrRMXszRyI91hjJ8/edit?usp=sharing
>Chinese proposal: https://shimo.im/docs/N2A1Mz9QZltQZoAD/
>Proposal sharing video: 
>https://meeting.tencent.com/v2/cloud-record/share?id=36398686-8f05-488b-acf7-91fef5498689&from=3

[ANNOUNCE]New Committers of Apache RocketMQ: HScarb(apache id:scarb)

[ShannonDing]

Hi Apache RocketMQ Community,




The Project Management Committee (PMC) for Apache RocketMQ has invited

HScarb(apache id:scarb),

to become a committer, and we are pleased to announce that he has accepted. 




Congrats, guy :-)

Re:[VOTE]Release Apache RocketMQ 4.9.4 RC1

[ShannonDing]

+1，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 ] Source code artifacts have correct names matching the current release.




At 2022-06-21 10:25:34, "hill"  wrote:

Hello RocketMQ Community,




This is the vote for 4.9.4 RC1 of Apache RocketMQ.

This release is to improve some features and issues for apache rocketmq,such as 
enhance acl , package dependency optimization,  improve encode/decode 
performance，fix some bugs and issues and so on.




The artifacts:

https://dist.apache.org/repos/dist/dev/rocketmq/4.9.4-rc1/




The staging repo:

https://repository.apache.org/content/repositories/orgapacherocketmq-1086/




Git tag for the release:

https://github.com/apache/rocketmq/releases/tag/rocketmq-all-4.9.4




Hash for the release tag:

06f2208a34907211591114f6b0d327168c250fb3




Release Notes:

https://rocketmq.apache.org/release_notes/release-notes-4.9.4




The artifacts have been signed with Key :

D011F2A8C9474A34099477A5C99B3EAC6B119386, 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:

[ ]  check LICENSE, should be Apache V2

[ ]  check NOTICE, should have a notice for third-party dependency if necessary

[ ]  extract the zip and check if the source version is correct

[ ]  verify the asc(PGP sign),SHA512

[ ]  build the source, start nameserver and broker according to the quick-start

[ ]  run clusterList command to see if the version is correct







The vote will be open for at least 72 hours or until the necessary number of 
votes are reached.

Please vote accordingly:




[ ] +1 approve

[ ] +0 no opinion

[ ] -1 disapprove with the reason




Thanks

The Apache RocketMQ Team













   

[ANNOUNCE]New Committer of Apache RocketMQ: Ni Ze(apache id:karp)

[ShannonDing]

Hi Apache RocketMQ Community,




The Project Management Committee (PMC) for Apache RocketMQ has invited

Ni Ze(apache id:karp),

to become a committer, and we are pleased to announce that he has accepted. 




Congrats, guy :-)




Best Wishes,

ShannonDing

Re:[ANNOUNCE]New Committers of Apache RocketMQ: Lin Shen(shenlin) and Yangkun Ai(aaronai)

[ShannonDing]

Congrats.

At 2022-06-15 10:10:34, "yukon"  wrote:

Hi Apache RocketMQ Community,

The Project Management Committee (PMC) for Apache RocketMQ has invited Lin Shen 
(apache id: shenlin, github id: 2011shenlin) and Yangkun Ai (apache id: 
aaronai, github id: aaron-ai) to become committers, and we are pleased to 
announce that they have accepted.

Congrats, guys :-)



Best regards,
Yukon

[ANNOUNCE]New Committers of Apache RocketMQ: Cai Gaoyang(apache id:caigy)

[ShannonDing]

Hi Apache RocketMQ Community,




The Project Management Committee (PMC) for Apache RocketMQ has invited

Cai Gaoyang(apache id:caigy),

to become a committer, and we are pleased to announce that he has accepted. 




Congrats, guy :-)




Best Wishes,

ShannonDing

Re:[VOTE][RIP-41]Build rocketmq e2e test and github action cicd

[ShannonDing]

+1

At 2022-05-05 10:46:18, "YuanchenZhang"  wrote:
>Hi, RocketMQ Community, 
>
>
>
>As discussed in the previous email, we launched a new RIP to support rocketmq 
>e2e test and github action cicd. Now the shepherds @duhenglucky are willing to 
>support the RIP, so I think it is time to start an email thread to enter the 
>voting process.
>
>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
>
>
>
>
>Best Regards!
>
>YuanchenZhang
>
>
>
>
>links: 
>
>https://docs.google.com/document/d/1NqVx7oXvJRnJA_qaZk-MH193i5at9KXPb7q2TRji8go/edit?usp=sharing
>
>https://shimo.im/docs/pmkxQEOZmDiLwdAN/
>
>

[ANNOUNCE]New Committers of Apache RocketMQ: Liang Yanjie(apache id: write2me)

[ShannonDing]

Hi Apache RocketMQ Community,




The Project Management Committee (PMC) for Apache RocketMQ has invited

Liang Yanjie(apache id: write2me),

to become a committer, and we are pleased to announce that he has accepted. 




Congrats, guy :-)




Best Wishes,

ShannonDing

[ANNOUNCE]New Committers of Apache RocketMQ: Wang Ping(apache id:pingww)

[ShannonDing]

Hi Apache RocketMQ Community,




The Project Management Committee (PMC) for Apache RocketMQ has invited

Wang Ping(apache id:pingww),

to become a committer, and we are pleased to announce that he has accepted. 




Congrats, guy :-)




Best Wishes,

ShannonDing

[ANNOUNCE]New Committers of Apache RocketMQ: Tian Liuhe(apache id:tianliuliu)

[ShannonDing]

Hi Apache RocketMQ Community,




The Project Management Committee (PMC) for Apache RocketMQ has invited

Tian Liuhe(apache id:tianliuliu),

to become a committer, and we are pleased to announce that he has accepted. 




Congrats, guy :-)




Best Wishes,

ShannonDing

Re:[VOTE][RIP-40] Quickly deploy of Apache Rocketmq Cluster

[ShannonDing]

+1,

At 2022-04-15 10:23:25, "孙先生"  wrote:
>Hi, RocketMQ Community, 
>
>
>
>
>As discussed in the previous email, we launched a new RIP to Quickly deploy 
>Apache Rocketmq Cluster. Now the shepherds @duhengforever are willing to 
>support the RIP, so I think it is time to start an email thread to enter the 
>voting process.
>
>
>
>
>
>
>
>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

Re:[RESTART][VOTE]Release Apache RocketMQ 5.0.0-ALPHA RC2

[ShannonDing]

+1,

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.




At 2022-03-11 11:43:46, "jinrongtong"  wrote:

Hello RocketMQ Community,


This is the vote for 5.0.0-alpha rc2 of Apache RocketMQ.
This release contains some important new features, including static topic and 
batch consume queue.


The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/5.0.0-ALPHA-rc2/


The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1083


Git tag for the release:
https://github.com/apache/rocketmq/tree/5.0.0-alpha


Hash for the release tag:
a17fa7605cfbd266e4468e6fe2d6cf6711572111


Release Notes:
https://rocketmq.apache.org/release_notes/release-notes-5.0.0-ALPHA/


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.
[]  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.
[]  Start nameserver and broker according to the quick-start
[]  Run clusterList command to see if the version is correct


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 5.0.0-ALPHA RC1

[ShannonDing]

+1,
Use Git tag for the release link: 
https://github.com/apache/rocketmq/tree/5.0.0-alpha




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.



At 2022-03-08 17:14:45, "jinrongtong"  wrote:

Hello RocketMQ Community,

This is the vote for 5.0.0-alpha of Apache RocketMQ.

This release contains some important new features, including static topic and 
batch consume queue.


The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/5.0.0-ALPHA-rc1/


The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1082


Git tag for the release:
https://github.com/apache/rocketmq/tree/5.0.0-alpha


Hash for the release tag:
be750f0e3340aea15c38368b3542888a5f40b8d9


Release Notes:
https://rocketmq.apache.org/release_notes/release-notes-5.0.0-ALPHA/


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.
[]  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.
[]  Start nameserver and broker according to the quick-start
[]  Run clusterList command to see if the version is correct


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:Re: [VOTE]: Release Apache RocketMQ 4.9.3 RC1

[ShannonDing]

+1 




[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 ] Source code artifacts have correct names matching the current release.
[OK ] Build the source, start nameserver and broker according to the 
quick-start.
At 2022-02-25 14:53:01, "caigy"  wrote:
>
>+1 
>I 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]  Build the source, start nameserver and broker according to the 
>quick-start.
>[OK]  Run cluster list command to see if the version is correct
>
>
>
>在 2022-02-25 14:27:56，"Amber Liu"  写道：
>>+1
>>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]  Start nameserver and broker according to the quick-start.
>>
>>nize  于2022年2月24日周四 11:05写道：
>>
>>> +1
>>> 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] All UT can pass
>>> [OK] Start nameserver and broker according to the quick-start
>>>
>>>
>>> heng du  于2022年2月24日周四 09:59写道：
>>>
>>> > +1
>>> > I checked：
>>> > [OK] Hash and Tag in GitHub repo is matching the current artifacts.
>>> > [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] All UT can pass
>>> > [OK] Run cluster list command to see if the version is correct
>>> > [OK] Start nameserver and broker according to the quick-start
>>> >
>>> >
>>> > Rongtong Jin  于2022年2月23日周三 20:36写道：
>>> >
>>> > > +1
>>> > > I Checked
>>> > >
>>> > > [OK] Hash and Tag in GitHub repo is matching the current artifacts.
>>> > > [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] All UT can pass
>>> > >
>>> > >
>>> > > 2022-02-23 15:02:22"tiger lee" 写道：
>>> > >
>>> > > Hello RocketMQ Community,
>>> > >
>>> > > This is the vote for 4.9.3 RC1 of Apache RocketMQ.
>>> > > This release is to improve some features and issues for apache
>>> > > rocketmq,such as support for Multiple Directories Storage, improve
>>> > > performances, fix some bugs and issues and so on.
>>> > >
>>> > > The artifacts:
>>> > > https://dist.apache.org/repos/dist/dev/rocketmq/4.9.3-rc1/
>>> > >
>>> > > The staging repo:
>>> > >
>>> >
>>> https://repository.apache.org/content/repositories/orgapacherocketmq-1081
>>> > >
>>> > > Git tag for the release:
>>> > > https://github.com/apache/rocketmq/releases/tag/rocketmq-all-4.9.3
>>> > >
>>> > > Hash for the release tag:
>>> > > c7989f85744e65e24b43955c88987288487b4707
>>> > >
>>> > > Release Notes:
>>> > > https://rocketmq.apache.org/release_notes/release-notes-4.9.3
>>> > >
>>> > > The artifacts have been signed with Key :
>>> > > F32A2D46, which can be found in the keys file:
>>> > > https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
>>> > >
>>> > >
>>> > > The vote will be open for at least 72 hours or until the 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][RIP-34] Support quorum write and adaptive degradation in master-slave architecture

[ShannonDing]

+1


At 2022-02-12 10:48:40, "jinrongtong"  wrote:
>Hi, RocketMQ Community, 
>
>As discussed in the previous email, we launched a new RIP to support quorum 
>write and adaptive degradation in master-slave architecture. Now the shepherd 
>@duhenglucky is willing to support the RIP, so I think it is time to start an 
>email thread to enter the voting process.
>
>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
>
>
>Best Regards!
>Rongtong Jin
>
>
>links: 
>https://docs.google.com/document/d/1ENCJl83OGnmtPMAbxTqtEs9LOOIkMNkz3A9HZJHyI2o/edit?usp=sharing
>https://shimo.im/docs/WJptDyXgjc3h6C8R

Re:Re: Re: [VOTE] Creating an external logappender repository

[ShannonDing]

+1

在 2022-02-08 17:37:26，"dongeforever"  写道：
>+1
>
>Rongtong Jin  于2022年2月8日周二 17:35写道：
>
>> +1
>>
>> "倪泽" 写道：
>> > +1
>> >
>> > zhibo li  于2022年2月8日周二 17:10写道：
>> >
>> > > +1
>> > >
>> > > heng du  于2022年2月8日周二 16:40写道：
>> > >
>> > > > Dear community,
>> > > >
>> > > > This is the vote for moving the logappender[1] to the
>> > > rocketmq-externals[2]
>> > > > repo first because it seems that logappender has little to do with
>> the
>> > > core
>> > > > of Apache RocketMQ, and it can bring faster releases of logappender,
>> > > > decouple with the release cycles of Apache RocketMQ.
>> > > >
>> > > > 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
>> > > >
>> > > > [1] https://github.com/apache/rocketmq
>> > > > [2] https://github.com/apache/rocketmq-externals
>> > > >
>> > > >
>> > > >
>> > > > Thanks
>> > > > Henry
>> > > >
>> > > > heng du  于2022年1月21日周五 14:49写道：
>> > > >
>> > > > > Hi， Justin，
>> > > > > Thanks for your kindly reply,  sorry I didn't express it clearly,
>> and
>> > > we
>> > > > > do not intend to move this project out of the apache repository,
>> but
>> > > just
>> > > > > transfer it from the main repository[1] to another sub-repository
>> of
>> > > > apache
>> > > > > rocketmq[2]， there should be no IP and ICLA issues involved.
>> > > > >
>> > > > > [1] https://github.com/apache/rocketmq
>> > > > > [2] https://github.com/apache/rocketmq-externals
>> > > > >
>> > > > > Thanks
>> > > > > Henry
>> > > > >
>> > > > > Justin Mclean  于2021年12月17日周五 11:36写道：
>> > > > >
>> > > > >> Hi,
>> > > > >>
>> > > > >> I would consider this very carefully and in fact suggest that you
>> > > don’t
>> > > > >> do this. Work on ASF projects needs to happen in ASF repos. By
>> doing
>> > > it
>> > > > >> outside you are missing the legal protection the ASF gives you and
>> > > other
>> > > > >> benefits being inside an ASF project give yuo. If at a later
>> point it
>> > > > does
>> > > > >> need to be brought back then you may have issues with IP and
>> ICLAs.
>> > > > >>
>> > > > >> Kind Regards,
>> > > > >> Justin
>> > > > >
>> > > > >
>> > > >
>> > >
>>

Re:Re: [VOTE][RIP-32] Slave Acting Master Mode

[ShannonDing]

+1

At 2022-02-03 11:14:59, "heng du"  wrote:
>+1
>
>jinrongtong  于2022年2月3日周四 00:03写道：
>
>> Hi, RocketMQ Community,
>>
>> As discussed in the previous email, we launched a new RIP to support slave
>> acting master mode. Now the shepherd @duhenglucky is willing to support the
>> RIP, so I think it is time to start an email thread to enter the voting
>> process.
>>
>>
>> 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
>>
>>
>>
>>
>> Best Regards!
>> Rongtong Jin
>>
>>
>>
>>
>> links:
>>
>>
>> https://docs.google.com/document/d/1LCTkfem6wcV-PqWjzPAvaxgqFMCj3ymPakDrcodX9ic/edit?usp=sharing
>> https://shimo.im/docs/6CqVccXgtWgXCYwv/

Re:[VOTE][RIP-30] Support Compaction topic

[ShannonDing]

+1

At 2022-01-21 10:59:14, "Amber Liu"  wrote:
>Hi, RocketMQ Community,
>
>As discussed in the previous email[1], we launched a new RIP to Support
>Compaction topic. Now the shepherds @duhenglucky are willing to support the
>RIP, so I think it is time to start an email thread to enter the voting
>process.
>
>
>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
>
>
>Best Regards!
>
>
>links:
>https://lists.apache.org/thread/bm0ov3sy96vj49vq4v3yryry7pjg9dxm

Re:[VOTE][RIP-31] Support RocketMQ BrokerContainer

[ShannonDing]

+1

At 2022-01-21 10:22:48, "jinrongtong"  wrote:
>Hi, RocketMQ Community, 
>
>As discussed in the previous email, we launched a new RIP to support RocketMQ 
>BrokerContainer. Now the shepherds @duhenglucky and @odbozhou are willing to 
>support the RIP, so I think it is time to start an email thread to enter the 
>voting process.
>
>
>
>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
>
>
>
>
>Best Regards!
>Rongtong Jin
>
>
>links: 
>https://docs.google.com/document/d/1Rnh9QSZSRowHnjMyDr7JKiHc-_uxc4ycSumbtB_iKzg/edit?usp=sharing
>https://shimo.im/docs/xxY3QDqYvj6G6Gk9/

Re:Re: [VOTE] Release Apache RocketMQ Streams 1.0.0-preview RC2

[ShannonDing]

+1， 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.
At 2022-01-21 17:36:51, "倪泽"  wrote:
>+1
>
>I checked:
>
> Checksums and PGP signatures are valid for source package.
>
>Source code artifacts have correct names matching the current release.
>
> All files have license headers in source package if necessary.
>The code can be built success in the source package.
>
>Amber Liu  于2022年1月21日周五 17:26写道：
>
>> +1 (non-binding)
>> checked:
>> [✓]  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.
>>
>> 周波  于2022年1月18日周二 13:15写道：
>>
>> > Hello RocketMQ Community,
>> >
>> >
>> > This is the vote for the 1.0.0-preview release of Apache
>> RocketMQ-Streams.
>> >
>> > The artifacts:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-streams/1.0.0-preview-rc2/
>> >
>> > The staging repo:
>> >
>> https://repository.apache.org/content/repositories/orgapacherocketmq-1074
>> >
>> > Git tag for the release:
>> >
>> >
>> https://github.com/apache/rocketmq-streams/releases/tag/rocketmq-streams-1.0.0-preview
>> >
>> > Hash for the release tag:
>> > ec9d3dfef8db4ce6678e2cd84f6b498b34c87523
>> >
>> > Release Notes:
>> >
>> >
>> http://rocketmq.apache.org/release_notes/release-notes-rocketmq-streams-1.0.0-preview/
>> >
>> > The artifacts have been signed with Key :
>> > DA38AD870652D9961F82EDC4E2DED90716D986F7, 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,
>> > The Apache RocketMQ Team
>> >
>>

Re:Re: [VOTE][RIP-29] Optimize RocketMQ NameServer

[ShannonDing]

+1

在 2022-01-18 11:13:33，"vongosling"  写道：
>+1
>
>周波  于2022年1月18日周二 10:54写道：
>
>> +1
>>
>> jinrongtong  于2022年1月18日周二 10:28写道：
>>
>> > Hi, RocketMQ Community:
>> >
>> >
>> > As discussed in the previous email, we launched a new RIP to optimize
>> > RocketMQ nameserver. Now the shepherds @duhenglucky and @ShannonDing are
>> > willing to support the RIP, so I think it is time to start an email
>> thread
>> > to enter the voting process.
>> >
>> > 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
>> >
>> >
>> >
>> >
>> > Best Regards!
>> > Rongtong Jin
>> >
>> >
>> > Proposal link: https://shimo.im/docs/pXgKrCwxhCcTwPkx/
>>
>
>
>-- 
>Best Regards :-)

Re:Re: [VOTE][RIP-27] Auto batching in producer

[ShannonDing]

+1

At 2021-12-29 19:50:19, "Rongtong Jin"  wrote:
>+1
>
>"Mad" <1094592...@qq.com.INVALID>写道：
>> Hi RocketMQ Community,
>> 
>> This is the vote for the kickoff of RIP-27 Auto Batch in producer
>> 
>> RIP-26 has prepared to implement batchConsumeQueue, but the message needs to 
>> be packaged manually on the client side, so I want to implement an auto 
>> batching capability. Now the shepherds @RongtongJin are willing to support 
>> the RIP, so I think it is time to start an email thread to enter the voting 
>> process.
>> 
>> 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
>> 
>> 
>> Best Regards!
>> Guyinyou
>> 
>> 
>> RIP-27 Auto batching in producer
>> https://docs.google.com/document/d/1ydZrA-FNrjM52I4H72EM2yaNAEYpRHV5uUSmFgxhWUQ/edit#heading=h.l32rlf9jfklr

Re:Re: [RESTART][VOTE] Release Apache RocketMQ 4.9.2 RC3

[ShannonDing]

+1

At 2021-10-25 13:48:09, "heng du"  wrote:
>+1
>
>I checked:
>[OK]  Source code artifacts have correct names matching the current release.
>[OK]  Hash and Tag in GitHub repo are matching the current artifacts.
>[OK]  The code can be built success in the source package.
>[OK]  Start nameserver and broker according to the quick-start
>[OK]  Run clusterList command to see if the version is correct
>[OK]  The  staging repo in maven is OK
>[OK]  All unit tests can pass.
>
>panzhi  于2021年10月24日周日 下午10:16写道：
>
>> +1
>>
>> I checked:
>> [OK]  Source code artifacts have correct names matching the current
>> release.
>> [OK]  Hash and Tag in GitHub repo are matching the current artifacts.
>> [OK]  The code can be built success in the source package.
>> [OK]  Start nameserver and broker according to the quick-start
>> [OK]  Run cluster list command to see if the version is correct
>> [OK]  The  staging repo in maven is OK
>> [OK]  All unit tests can pass.
>>
>>
>>
>>
>>
>> -- 原始邮件 --
>> 发件人:
>>   "dev"
>> <
>> stylet...@apache.org>;
>> 发送时间: 2021年10月24日(星期天) 下午5:40
>> 收件人: "users"> 抄送: "dev"> 主题: Re: [RESTART][VOTE] Release Apache RocketMQ 4.9.2 RC3
>>
>>
>>
>> +1
>>
>> I checked:
>> [OK]  Source code artifacts have correct names matching the current
>> release.
>> [OK]  Hash and Tag in GitHub repo are matching the current artifacts.
>> [OK]  The code can be built success in the source package.
>> [OK]  Start nameserver and broker according to the quick-start
>> [OK]  Run cluster list command to see if the version is correct
>> [OK]  The  staging repo in maven is OK
>> [OK]  All unit tests can pass.
>>
>>
>> Rongtong Jin >
>> > +1
>> >
>> > I checked:
>> > [OK]  Source code artifacts have correct names matching the
>> current
>> > release.
>> > [OK]  Hash and Tag in GitHub repo is matching the current
>> artifacts.
>> > [OK]  The code can be built success in the source package.
>> > [OK]  Start nameserver and broker according to the quick-start
>> > [OK]  Run clusterList command to see if the version is correct
>> > [OK]  The  staging repo in maven is OK
>> > [OK]  All unit tests can pass.
>> >
>> > "Francis Lee" <francism...@gmail.com
>> >写道：
>> > > Hello RocketMQ Community,
>> > >
>> > > This is the vote for 4.9.2 of Apache RocketMQ.
>> > > This release is to improve some features and issues for apache
>> > > rocketmq,such as support for Multiple Directories Storage,
>> improve
>> > > performances, fix some bugs and issues and so on.
>> > >
>> > > The artifacts:
>> > > https://dist.apache.org/repos/dist/dev/rocketmq/4.9.2-rc3/
>> > >; >
>> > > The staging repo:
>> > >
>> >
>> https://repository.apache.org/content/repositories/orgapacherocketmq-1071
>> >
>> >;
>> >
>> > > Git tag for the release:
>> > >
>> https://github.com/apache/rocketmq/releases/tag/rocketmq-all-4.9.2
>> >
>> >;
>> >
>> > > Hash for the release tag:
>> > > c840b208337b26c7529602b81d398c0a87a23888
>> > >
>> > > Release Notes:
>> > > https://rocketmq.apache.org/release_notes/release-notes-4.9.2/
>> > >;
>> >
>> > > The artifacts have been signed with Key :
>> > > F32A2D46, which can be found in the keys file:
>> > > https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
>> > >
>> > >
>> > > The vote will be open for at least 72 hours or until the
>> necessary number
>> > > of votes are reached.
>> > > Please vote accordingly:
>> > >
>> > > [ ] +1 approve
>> > > [ ] +0 no opinion
>> > > [ ] -1 disapprove with the reason
>> > >
>> > > Thanks
>> > > The Apache RocketMQ Team
>> >

[ANNOUNCE]New Committers of Apache RocketMQ: Lin Qingshan(apache id:linhill)

[ShannonDing]

Hi Apache RocketMQ Community,




The Project Management Committee (PMC) for Apache RocketMQ has invited

Lin Qingshan(apache id:linhill),

to become a committer, and we are pleased to announce that he has accepted. 




Congrats, guy :-)




Best Wishes,

ShannonDing

[DISCUSS]Release Apache rocketmq-client-go 2.1.1

[ShannonDing]

Hello RocketMQ Community,




Apache RocketMQ team is about to release Apache rocketmq-client-go 2.1.1 and we 
will stop merge PR.

 If your PR has not been merged and needs further attention, please reply to 
this email and we will review it as soon as possible.




Best Regards,

Apache RocketMQ Team.

​[ANNOUNCE]New Committers of Apache RocketMQ: Li Zhibo(apache id:osgooli)

[ShannonDing]

Hi Apache RocketMQ Community,




The Project Management Committee (PMC) for Apache RocketMQ has invited

Li Zhibo(apache id:osgooli),

to become a committer, and we are pleased to announce that he has accepted. 




Congrats, guy :-)




Best Wishes,

ShannonDing

Re:Re: Re: [VOTE]Release Apache RocketMQ Spring 2.2.1 RC1

[ShannonDing]

+1，

 checked：
[ok] Source code artifacts have correct names matching the current release.
[ok] License and Notice are correct in the source package.
[ok] All files have license headers in the source package if necessary.
[ok] No compiled archives bundled in the source archive.
[ok] Hash and Tag in GitHub repo are matching the current artifacts.

At 2021-09-04 10:46:56, "Rongtong Jin"  wrote:
>+1， I checked
>1.Source code artifacts have correct names matching the current release.
>2.Git tag page has correct release version for rocketmq version
>3.Hash and Tag in GitHub repo are matching the current artifacts.
>4.Source code can built and compile successfully.
>
>
>"倪泽" 写道：
>> +1
>> [ok] check artifacts has correct names and release version.
>> [ok] Git tag page has correct release version for rocketmq version, and
>> source code zip package.
>> [ok] Hash and Tag in GitHub repo are matching the current artifacts.
>> [ok]All files have license headers in source package if necessary.
>> [ok] source code can built and compile successfully.
>> 
>> heng du  于2021年9月3日周五 下午12:28写道：
>> 
>> > +1
>> >
>> > checked：
>> >
>> > [[ok] Source code artifacts have correct names matching the current
>> > release.
>> > [ok] License and Notice are correct in the source package.
>> > [ok] All files have license headers in the source package if necessary.
>> > [ok] No compiled archives bundled in the 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.
>> >
>> > jinrongtong  于2021年8月31日周二 下午6:57写道：
>> >
>> > > Hello RocketMQ Community,
>> > >
>> > >
>> > >
>> > > This is the vote for the 2.2.1 release of Apache RocketMQ-Spring.
>> > >
>> > >
>> > > The artifacts:
>> > >
>> > https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-spring/2.2.1-rc1/
>> > >
>> > >
>> > > The staging repo:
>> > >
>> > https://repository.apache.org/content/repositories/orgapacherocketmq-1060
>> > >
>> > >
>> > > Git tag for the release:
>> > >
>> > >
>> > https://github.com/apache/rocketmq-spring/releases/tag/rocketmq-spring-all-2.2.1
>> > >
>> > >
>> > > Hash for the release tag:
>> > > 7fbcc85e1161154a60a94e1b0e654c19443bf160
>> > >
>> > >
>> > > Release Notes:
>> > >
>> > >
>> > http://rocketmq.apache.org/release_notes/release-notes-rocketmq-spring-2.2.1/
>> > >
>> > >
>> > > 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,
>> > > The Apache RocketMQ Team
>> >

Re:[VOTE]:Release Apache RocketMQ 4.9.1 RC1.

[ShannonDing]

+1,
checked:
[OK]  Source code artifacts have correct names matching the current release.
[OK]  Hash and Tag in GitHub repo is matching the current artifacts.
[OK]  The code can be built success in the source package.
[OK]  Start nameserver and broker according to the quick-start
[OK]  Run clusterList command to see if the version is correct















At 2021-08-18 14:25:30, "胡 宗棠"  wrote:
>Hello RocketMQ Community,
>
>
>This is the vote for 4.9.1 of Apache RocketMQ.
>
>
>This release is to improve some features and issues for apache rocketmq,such 
>as improving rocketmq's remarkable throughput performance for pub/sub messages 
>, fix some bugs and issue for acl and code-style,  adding some new benchmarks 
>and examples and so on.
>
>
>The artifacts:
>
>https://dist.apache.org/repos/dist/dev/rocketmq/4.9.1-rc1/
>
>
>The staging repo:
>
>https://repository.apache.org/content/repositories/orgapacherocketmq-1056
>
>
>Git tag for the release:
>
>https://github.com/apache/rocketmq/releases/tag/rocketmq-all-4.9.1
>
>
>Hash for the release tag:
>
>a1bfe1afce40c08083cae770b777aa2c9067479d
>
>
>Release Notes:
>
>https://rocketmq.apache.org/release_notes/release-notes-4.9.1/
>
>
>The artifacts have been signed with Key :
>
>5C7C4040979F32543B624C631DA2409169DAF54B, which can be found in the keys
>
>file:
>
>https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
>
>
>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 4.9.0 RC1.

[ShannonDing]

+1,
checked:

[OK ]  Checksums and PGP signatures are valid for the Source package.

[OK ]  Source code artifacts have correct names matching the current release.

[OK ]  License and Notice are correct in the source package.

[OK ]  All files have license headers in the source package if necessary.

[OK ]  Hash and Tag in GitHub repo are matching the current artifacts.


At 2021-06-11 23:33:41, "胡 宗棠"  wrote:
>Hello RocketMQ Community,
>
>
>This is the vote for 4.9.0 of Apache RocketMQ.
>
>
>This release is to improve some features for apache rocketmq,such as
>
>supporting producer and cunsumer opentracing, lite pull consumer messaging 
>trace, enhancing some stability in unit test cases,
>
>enhancing some parameter validation in the rocketmq acl module, adding some 
>new mqadmin command and so on.
>
>
>
>The artifacts:
>
>https://dist.apache.org/repos/dist/dev/rocketmq/4.9.0-rc1/
>
>
>The staging repo:
>
>https://repository.apache.org/content/repositories/orgapacherocketmq-1053/
>
>
>Git tag for the release:
>
>https://github.com/apache/rocketmq/releases/tag/rocketmq-all-4.9.0
>
>
>Hash for the release tag:
>
>5203d52f1bab431ada236ba279c80e62778f8a15
>
>
>Release Notes:
>
>https://rocketmq.apache.org/release_notes/release-notes-4.9.0/
>
>
>The artifacts have been signed with Key :
>
>5C7C4040979F32543B624C631DA2409169DAF54B, which can be found in the keys
>
>file:
>
>https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
>
>
>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
>

[DISCUSS]Release Apache RocketMQ 4.8.1

[ShannonDing]

Hello RocketMQ Community,


Apache RocketMQ team is about to release Apache RocketMQ 4.8.1 and we will 
stop merge PR. If your PR has not been merged and needs further attention, 
please reply to this email and we will review it as soon as possible.


Best Regards,
Apache RocketMQ Team.

[ANNOUNCE]New Committer of Apache RocketMQ: Zhang Xu(apache id: maixiaohai)

[ShannonDing]

Hi Apache RocketMQ Community,




The Project Management Committee (PMC) for Apache RocketMQ has invited

Zhang Xu(apache id: maixiaohai),

to become a committer, and we are pleased to announce that he has accepted. 




Congrats, guy :-)




Best Wishes,

ShannonDing

[ANNOUNCE] Release Apache RocketMQ Client Native Go 2.1.0

[ShannonDing]

Hello RocketMQ Community,




The Apache RocketMQ team would like to announce the release of Apache RocketMQ 
Client Native Go 2.1.0.

The main goal of this release is to improve stability, usability, and fix bugs 
and the source code of this release is the copy of the master which has merged 
from the native branch before.




The release artifacts can be downloaded here:

https://mirrors.tuna.tsinghua.edu.cn/apache/rocketmq/rocketmq-client-go/2.1.0/rocketmq-client-go-2.1.0-source-release.tar.gz




The release notes can be found here:

http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-go-2.1.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




Thanks,

The Apache RocketMQ Team

[RESULT][VOTE]Release Apache RocketMQ Client Go Native 2.1.0.

[ShannonDing]

Hello RocketMQ Community,




The Apache RocketMQ Client Go Native vote is now closed and has passed with [3] 
binding +1s, [2] non-binding +1s, and no 0 or -1:




*Binding votes +1s:*




ShannonDing(ding...@apache.org)

Du Heng(duhengfore...@apache.org)

Jin Rongtong(jinrongt...@apache.org)




*Non-binding votes +1s:*

maixiaoha...@gmail.com

zongtan...@hotmail.com




The release will be published soon.




Thanks,

The Apache RocketMQ Team

Re:Re: Re: [VOTE]Release Apache RocketMQ Client Go Native 2.1.0.

[ShannonDing]

+1


At 2021-03-22 14:00:37, "Rongtong Jin"  wrote:
>+1, I checked
>
>[ ok]  Checksums and PGP signatures are valid for the Source package.
>
>[ ok] Source code artifacts have correct names matching the current release.
>
>[ ok] License and Notice are correct in the source package.
>
>[ ok]  All files have license headers in the source package if necessary.
>
>"heng du" <duhengfore...@apache.org>写道：
>> +1
>> 
>> [ ok]  Checksums and PGP signatures are valid for the Source package.
>> 
>> [ ok] Source code artifacts have correct names matching the current release.
>> 
>> [ ok] License and Notice are correct in the source package.
>> 
>> [ ok]  All files have license headers in the source package if necessary.
>> 
>> [ ok]   No compiled archives bundled in the source archive.
>> 
>> [ ok] Hash and Tag in GitHub repo are matching the current artifacts.
>> 
>> 胡 宗棠  于2021年3月19日周五 上午10:31写道：
>> 
>> > +1
>> > checked
>> >
>> > 
>> > 发件人: zhang xu 
>> > 发送时间: 2021年3月18日 22:10
>> > 收件人: dev@rocketmq.apache.org 
>> > 主题: Re: [VOTE]Release Apache RocketMQ Client Go Native 2.1.0.
>> >
>> > +1
>> > checked
>> >
>> > [ OK ]  Source code artifacts have correct names matching the current
>> > release.
>> >
>> > [ OK ]  License and Notice are correct in the source package.
>> >
>> > [ OK ]  All files have license headers in the source package if necessary.
>> >
>> > [ OK ]  No compiled archives bundled in the source archive.
>> >
>> > [ OK ]  Hash and Tag in GitHub repo are matching the current artifacts.
>> >
>> > ShannonDing  于2021年3月18日周四 下午9:09写道：
>> >
>> > > Hello RocketMQ Community,
>> > >
>> > >
>> > >
>> > > This is the vote for version 2.1.0 of Apache RocketMQ Client Go Native.
>> > >
>> > > The main goal of this release is to improve stability, usability, and fix
>> > > bugs and the source code of this release is the copy of the master which
>> > > has merged from the native branch before.
>> > >
>> > > The artifacts:
>> > >
>> > >
>> > >
>> > https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-go/2.1.0-rc6/
>> > >
>> > > Git tag for the release:
>> > >
>> > > https://github.com/apache/rocketmq-client-go/releases/tag/v2.1.0
>> > >
>> > > The hash for the release tag:
>> > >
>> > > d6e66a2d648d6529eca833f9bf912915d1749a5c
>> > >
>> > > Release Notes:
>> > >
>> > >
>> > >
>> > http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-go-2.1.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 an official policy but may help with checking
>> > > releases.
>> > >
>> > > Fill in the following:
>> > >
>> > > [ ]  Checksums and PGP signatures are valid for the Source package.
>> > >
>> > > [ ]  Source code artifacts have correct names matching the current
>> > release.
>> > >
>> > > [ ]  License and Notice are correct in the source package.
>> > >
>> > > [ ]  All files have license headers in the source package if necessary.
>> > >
>> > > [ ]  No compiled archives bundled in the source archive.
>> > >
>> > > [ ]  Hash and Tag in GitHub repo are matching the current artifacts.
>> > >
>> > > As we don’t release binary packages for Apache RocketMQ Go SDK, the
>> > binary
>> > > package checklist should not be followed.
>> > >
>> > > 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 the necessary number
>> > > of votes are reached.
>> > >
>> > > Please vote accordingly:
>> > >
>> > >
>> > >
>> > >
>> > > [ ] +1 approve
>> > >
>> > > [ ] +0 no opinion
>> > >
>> > > [ ] -1 disapprove with the reason
>> > >
>> > >
>> > >
>> > >
>> > > Thanks,
>> > >
>> > > The Apache RocketMQ Team
>> >

[VOTE]Release Apache RocketMQ Client Go Native 2.1.0.

[ShannonDing]

Hello RocketMQ Community,



This is the vote for version 2.1.0 of Apache RocketMQ Client Go Native.

The main goal of this release is to improve stability, usability, and fix bugs 
and the source code of this release is the copy of the master which has merged 
from the native branch before.

The artifacts:

https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-go/2.1.0-rc6/

Git tag for the release:

https://github.com/apache/rocketmq-client-go/releases/tag/v2.1.0

The hash for the release tag:

d6e66a2d648d6529eca833f9bf912915d1749a5c

Release Notes:

http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-go-2.1.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 an official policy but may help with checking releases.

Fill in the following:

[ ]  Checksums and PGP signatures are valid for the Source package.

[ ]  Source code artifacts have correct names matching the current release.

[ ]  License and Notice are correct in the source package.

[ ]  All files have license headers in the source package if necessary.

[ ]  No compiled archives bundled in the source archive.

[ ]  Hash and Tag in GitHub repo are matching the current artifacts.

As we don’t release binary packages for Apache RocketMQ Go SDK, the binary 
package checklist should not be followed.

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 the necessary number of 
votes are reached.

Please vote accordingly:




[ ] +1 approve

[ ] +0 no opinion

[ ] -1 disapprove with the reason




Thanks,

The Apache RocketMQ Team

[DISCUSS]Release Apache rocketmq-client-go Native 2.1.0

[ShannonDing]

Hello RocketMQ Community,




Apache RocketMQ team is about to release Apache rocketmq-client-go Native 2.1.0 
and we will stop merge PR.

 If your PR has not been merged and needs further attention, please reply to 
this email and we will review it as soon as possible.




Best Regards,

Apache RocketMQ Team.

[ANNOUNCE]New Committer of Apache RocketMQ:Li Huang(apache id: huangli)

[ShannonDing]

Hi Apache RocketMQ Community,


The Project Management Committee (PMC) for Apache RocketMQ has invited
Li Huang(apache id: huangli),
to become a committer, and we are pleased to announce that he has accepted. 


Congrats, guy :-)


Best Wishes,
ShannonDing

Re: [VOTE] RIP-19 RocketMQ Pop Consuming

[ShannonDing]

+1. This greatly improves the ease of use of the client and reduces the 
difficulty for developers to access the system.


On 01/19/2021 23:24，Rongtong Jin wrote：
+1, IMO, it is a good solution to solve some important issues of queue load 
balancing.

2021-01-18 14:37:27"heng du" 写道：

Hi RocketMQ Community,

This is the vote for the kickoff of RIP-19 RocketMQ Pop Consuming.

In order to better implement a lightweight client, @ayanamist proposes a new 
consumption model, and at the same time transfers the load balancing logic of 
the original client to the broker, which not only solves the original queue 
occupancy problem but also It can also avoid the consumption delay caused by a 
certain consumer hangs.


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




Best Regards!
Henry



ayanamist  于2021年1月8日周五 上午11:25写道：

# RIP-19 RocketMQ Pop Consuming

# Status

- Current State: Proposed
- Authors: [ayanamist]([
https://github.com/ayanamist/](https://github.com/ayanamist/))
- Shepherds: [duhengforever]([
https://github.com/duhenglucky/](https://github.com/duhengforever/))
- Mailing List discussion: dev@rocketmq.apache.org;
us...@rocketmq.apache.org
- Pull Request: RIP-19
- Released: -

# Background & Motivation

### What do we need to do

- Will we add a new module?

No.

- Will we add new APIs?

Yes.

- Will we add new feature?

Yes.

### Why should we do that

- Are there any problems of our current project?

The current subscription load balancing strategy is based on the
dimension of message queue. All behaviors are owned by the client side.
There are three main steps:

1. Each consumer regularly obtains the total number of topic message
queues and all consumers.
2. Using a general algorithm to sort the queues by consumer ip and
queue index to calculate which message queue is allocated to which consumer.
3. Each consumer pulls messages using allocated orders described above.

According to this allocation method, if an abnormality occurs in a
consumer (the application itself is abnormal, or a broker is upgrading) so
that it causes slow subscription, messages will be accumulated, but this
queue will not be re-allocated to another consumer, so the accumulation
will become more and more serious.


Chinese version:

当前的消费负载均衡策略是以队列的维度来进行，所有行为全部是由客户端主动来完成，主要分为三步：

1. 每个consumer定时去获取消费的topic的队列总数，以及consumer总数
2. 将队列按编号、consumer按ip排序，用统一的分配算法计算该consumer分配哪些消费队列
3. 每个consumer去根据算法分配出来的队列，拉取消息消费


按照这个分配方式，如果有一个队列有异常（应用自身异常，或某个broker在升级）导致消费较慢或者停止，该队列会出现堆积现象，因为队列不会被分配给其他机器，因此如果长时间不处理，队列的堆积会越来越严重。

- What can we benefit proposed changes?

The accumulated messages will be subscribed by other consumers if one
consumer behaves abnormally.

Chinese version:

在某个队列消费异常的情况下，可以快速的由其它消费者接手进行消费，缓解堆积状态。

# Goals

- What problem is this proposal designed to solve?

The accumulated messages will be subscribed by other consumers if one
consumer behaves abnormally.

Chinese version:

在某个队列消费异常的情况下，可以快速的由其它消费者接手进行消费，缓解堆积状态。

- To what degree should we solve the problem?

This RIP must guarantee below point:

1. High availablity: Subscription of one message queue will not be
affected by single consumer failure.
2. High performance: This implementation affects latency and throughput
less than 10%.


Chinese version:

新方案需要保证两点：

1. 高可用：单一队列的消费能力不受某个消费客户端异常的影响
2. 高性能：POP订阅对消息消费的延迟和吞吐的影响在10%以内

# Non-Goals

- What problem is this proposal NOT designed to solve?

Improve client-side load balancing.

- Are there any limits of this proposal?

Nothing specific.

# Changes

## Architecture

Current "Pull mode":
![pull](
https://user-images.githubusercontent.com/406779/103756075-cc93b900-5049-11eb-8fae-cfe5398ebaad.png
)

Proposed "Pop mode":
![pop](
https://user-images.githubusercontent.com/406779/103757230-6d36a880-504b-11eb-95d5-7e8cff8cdef1.png
)

Move inter-queue balance of one topic from client side to server side.
Clients make pull request without specified queues to broker, and broker
fetch messages from queues internally and returns, which ensures one queue
will be consumed by multiple clients. The whole behavior is like a queue
pop process.

It will add a new request command querying queue assignments in broker, and
add pop-feature-support flag to pull request which makes broker use pop
mode.

## Interface Design/Change

- Method signature changes

Nothing specific.

- Method behavior changes

Nothing specific.

- CLI command changes

Add `setConsumeMode` for admin to switch between old pull mode and new
pop mode for one subscription.

- Log format or content changes

Nothing specific.

## Compatibility, Deprecation, and Migration Plan

- Are backward and forward compatibility taken into consideration?

New RequestCode between client and broker are added, so there are 2
compatibility situations:

1. old client+new broker: old clients won't make request with
pop-feature-support flag, so br

Re: [VOTE]Release Apache RocketMQ Spring 2.2.0 RC1

[ShannonDing]

+1,


[OK]  Checksums and PGP signatures are valid for 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.


On 01/10/2021 10:22，金融通 wrote：
+1




[OK]  Checksums and PGP signatures are valid for source package.

[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.



-原始邮件-
发件人:jinrongtong 
发送时间:2021-01-08 19:23:15 (星期五)
收件人: "dev@rocketmq.apache.org" 
抄送: "us...@rocketmq.apache.org" 
主题: [VOTE]Release Apache RocketMQ Spring 2.2.0 RC1



Hello RocketMQ Community,

This is the vote for the 2.2.0 release of Apache RocketMQ-Spring.


The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-spring/2.2.0-rc1/


The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1050


Git tag for the release:
https://github.com/apache/rocketmq-spring/releases/tag/rocketmq-spring-all-2.2.0


Hash for the release tag:
66a6d8b51c6202b14195b1ac1a4311a7ce3e81dc


Release Notes:
http://rocketmq.apache.org/release_notes/release-notes-rocketmq-spring-2.2.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,
The Apache RocketMQ Team

Re: [VOTE]Release Apache RocketMQ 4.8.0 RC1

[ShannonDing]

+1 binding,
checked:
[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]  Hash and Tag in GitHub repo is matching the current artifacts.




On 12/16/2020 19:26，Rongtong Jin wrote：
+1

I checked:
[OK]  Source code artifacts have correct names matching the current release.
[OK]  Hash and Tag in GitHub repo is matching the current artifacts.
[OK]  The code can be built success in the source package.
[OK]  Start nameserver and broker according to the quick-start
[OK]  Run clusterList command to see if the version is correct

"jinrongtong" 写道：
Hello RocketMQ Community,

This is the vote for 4.8.0 of Apache RocketMQ.

This release has made a lot of optimizations to the DLedger mode, including 
supporting batch messages, optimizing replication to improve performance, and 
fixing important bugs. This release made some enhancements, such as adding a 
query message trace command, using CopyOnWriteArrayList to avoid possible 
thread safety issues. Finally, this release optimized a large number of 
documents and code style.


The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/4.8.0-rc1/


The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1049


Git tag for the release:
https://github.com/apache/rocketmq/tree/release-4.8.0


Hash for the release tag:
39bb9386f10d5d8dfe81183c172a3a86f6d313bd


Release Notes:
https://rocketmq.apache.org/release_notes/release-notes-4.8.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.
[]  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.
[]  Start nameserver and broker according to the quick-start
[]  Run clusterList command to see if the version is correct


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 RocketMQ Spring 2.1.1 RC1

[ShannonDing]

+1 (binding)


[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.
On 07/24/2020 15:25，heng du wrote：
Hi,

+1 (binding)

[ok]  The code can be built success in the source package
[ok]  Send and receive messages with the broker.
[ok]  Source code artifacts have correct names matching the current release.
[ok]  No compiled archives bundled in the source archive.



Justin Mclean  于2020年7月23日周四 下午5:02写道：

Hi,

+1 (binding)

I checked:
- signatures and hashes are correct
- LICENSE and NOTICE are correct
- All file have ASF headers
- No binary files
- can compile from source

Thanks,
Justin

Re: [RESTART][VOTE][#1] Release Apache RocketMQ 4.7.1 RC2

[ShannonDing]

+1 (binding)


I 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.




On 06/24/2020 16:15，zhibo li wrote：
+1
[√ ]  The code can be built success in the source package.

jinrongtong  于2020年6月24日周三 下午3:36写道：

Hello RocketMQ Community,

This is the vote for 4.7.1 of Apache RocketMQ.

This release made some enhancements, such as the upgrade of fastjson
version, improving the security of the system topic operation, optimizing
master-slave replication, pull consumer, etc. This release also fixed issue
about request-reply message. Finally, this release optimized a large number
of documents and code style.


The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/4.7.1-rc2/


The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1047


Git tag for the release:
https://github.com/apache/rocketmq/commits/release-4.7.1


Hash for the release tag:
9f95a972e10e0681bc3f2d00e9957aa212e897b5


Release Notes:
https://rocketmq.apache.org/release_notes/release-notes-4.7.1/


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 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.
[]  Start nameserver and broker according to the quick-start
[]  Run clusterList command to see if the version is correct


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

[SECURITY][CVE-2019-17572] Apache RocketMQ directory traversal vulnerability

[ShannonDing]

Hi, 
An directory traversal vulnerability[1] was discovered in the version RocketMQ 
4.6.0 and it affect all
versions earlier. And it was fixed in the version 4.6.1 and later according to 
the CVE-2019-17572.
Here is the detail of the vulnerability below:


[CVEID]:CVE-2019-17572
[PRODUCT]:Apache RocketMQ
[VERSIONS]:Apache RocketMQ 4.2.0 to 4.6.0
[PROBLEMTYPE]: Directory traversal vulnerability
[REFERENCES]:https://lists.apache.org/thread.html/fdea1c5407da47a17d5522fa149a097cacded1916c1c1534d46edc6d%40%3Cprivate.rocketmq.apache.org%3E
[DESCRIPTION]:When the automatic topic creation in the broker is turned on by 
default, an evil topic like “../../../../topic2020” is sent from 
rocketmq-client to the broker,  a topic folder will be created in the parent 
directory in brokers, which leads to a directory traversal vulnerability.
[MITIGATION]: Users of the affected versions should apply one of the following:
mitigations:
- Upgrade to Apache RocketMQ 4.6.1or later


[1] https://github.com/apache/rocketmq/issues/1637

[ANNOUNCE]New Committers of Apache RocketMQ: Jianhai Xu(jianhaixu)

[ShannonDing]

Hi Apache RocketMQ Community,


The Project Management Committee (PMC) for Apache RocketMQ has invited
Jianhai Xu(apache id: jianhaixu),
to become a committer, and we are pleased to announce that he has accepted. 
Congrats, guy :-)


Best Wishes,
ShannonDing

[ANNOUNCE]New Committers of Apache RocketMQ: Xiangwang Cheng(changxiangwang)

[ShannonDing]

Hi Apache RocketMQ Community,


The Project Management Committee (PMC) for Apache RocketMQ has invited
Xiangwang Cheng(apache id: chengxiangwang),
to become a committer, and we are pleased to announce that he has accepted. 


Congrats, guy :-)


Best Wishes,
ShannonDing

[RESULT][VOTE]Release Apache RocketMQ Client CPP 2.2.0 RC1.

[ShannonDing]

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 (vongosl...@apache.org)
ShannonDing(ding...@apache.org)
Jin Rongtong(jinrongt...@apache.org)
Li Qipeng(wlliqip...@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.

[ShannonDing]

+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 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

[VOTE]Release Apache RocketMQ Client CPP 2.2.0 RC1.

[ShannonDing]

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

[ANNOUNCE] Release Apache RocketMQ Client Native Go 2.0.0

[ShannonDing]

Hello RocketMQ Community,


The Apache RocketMQ team would like to announce the release of Apache RocketMQ 
Client Native Go 2.0.0.
For the first product ready RocketMQ Client in pure go, it supports almost the 
full features of Apache RocketMQ, such as pub and sub messages, ACL, tracing 
and so on.


The release artifacts can be downloaded here:
https://mirrors.tuna.tsinghua.edu.cn/apache/rocketmq/rocketmq-client-go/2.0.0/rocketmq-client-go-2.0.0-source-release.tar.gz


The release notes can be found here:
http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-go-2.0.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


Thanks,
The Apache RocketMQ Team

[RESULT][VOTE]Release Apache RocketMQ Client Go Native 2.0.0.

[ShannonDing]

Hello RocketMQ Community,


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


*Binding votes +1s:*


Gosling Von (vongosl...@apache.org)
ShannonDing(ding...@apache.org)
Du Heng(duhengfore...@apache.org)
Jin Rongtong(jinrongt...@apache.org)
Li Qipeng(wlliqip...@apache.org）


The release will be published soon.


Thanks,
The Apache RocketMQ Team

[DISCUSS]Release Apache rocketmq-client-cpp 2.2.0

[ShannonDing]

Hello RocketMQ Community,


Apache RocketMQ team is about to release Apache rocketmq-client-cpp 2.2.0 and 
we will stop merge PR.
 If your PR has not been merged and needs further attention, please reply to 
this email and we will review it as soon as possible.


Best Regards,
Apache RocketMQ Team.

[ANNOUNCE] New PMC member for Apache RocketMQ

[ShannonDing]

Hi Apache RocketMQ Community,


The Project Management Committee (PMC) for Apache RocketMQ has invited Rongtong 
Jin(apache id: jinrongtong) 
to become PMC Member and we are pleased to announce that he has accepted.


Congrats, guy :-)


RongtongJin[1,2,3,4,5], spends a lot of time on improving the usability of 
RocketMQ eco system. He
implements a new Pull Consumer client for RocketMQ, and continues to optimize 
the rocketmq-spring and
do a full Jepsen test on RocketMQ and so on. at the same time, as a release 
manager, he spent much time in
expanding the community and he helped the community released rocketmq 4.6.0, 
4.6.1, 4.7.0 and
rocketmq-spring 2.1.0, and he is still planning to release new versions.


[1]https://github.com/apache/rocketmq/commits?author=RongtongJin
[2]https://github.com/apache/rocketmq-spring/commits?author=RongtongJin
[3]https://github.com/apache/rocketmq-site/commits?author=RongtongJin
[4]https://lists.apache.org/list.html?dev@rocketmq.apache.org:lte=3M:RongtongJin
[5]https://lists.apache.org/list.html?dev@rocketmq.apache.org:lte=3M:Rongtong%20Jin


Best Regards,
Apache RocketMQ Team

[VOTE]Release Apache RocketMQ Client Go Native 2.0.0.

[ShannonDing]

Hello RocketMQ Community,


This is the vote for version 2.0.0 of Apache RocketMQ Client Go Native.
For the first product ready RocketMQ Client in pure go, it supports almost the 
full features of Apache RocketMQ, such as pub and sub messages, ACL, message 
tracing and so on.
The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-go/2.0.0-rc3/
Git tag for the release:
https://github.com/apache/rocketmq-client-go/releases/tag/v2.0.0
Hash for the release tag:
be579956f83854915f9742578e8db81860b71112
Release Notes:
http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-go-2.0.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.
[ ]  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 is matching the current artifacts.
As we don’t release binary package for Apache RocketMQ Go SDK, the binary 
package checklist should not be followed.
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

[DISCUSS]Release Apache rocketmq-client-go Native 2.0.0

[ShannonDing]

Hello RocketMQ Community,


Apache RocketMQ team is about to release Apache rocketmq-client-go Native 2.0.0 
and we will stop merge PR.
 If your PR has not been merged and needs further attention, please reply to 
this email and we will review it as soon as possible.


Best Regards,
Apache RocketMQ Team.

[ANNOUNCE] Release Apache RocketMQ Client CPP 2.1.0

[ShannonDing]

Hello RocketMQ Community,




The Apache RocketMQ team would like to announce the release of Apache RocketMQ 
Client CPP 2.1.0.

This release is a major upgrade, mainly including message tracing for pub and 
sub and support for higher version of GCC and add asan/lsan to check memories. 




The release artifacts can be downloaded here:

https://mirrors.tuna.tsinghua.edu.cn/apache/rocketmq/rocketmq-client-cpp/2.1.0/rocketmq-client-cpp-2.1.0-source-release.tar.gz

https://mirrors.tuna.tsinghua.edu.cn/apache/rocketmq/rocketmq-client-cpp/2.1.0/rocketmq-client-cpp-2.1.0-bin-release.tar.gz




The release notes can be found here:

http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-2.1.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




Thanks,

The Apache RocketMQ Team

[RESULT][VOTE]Release Apache RocketMQ Client CPP 2.1.0 RC1.

[ShannonDing]

Hello RocketMQ Community,


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


*Binding votes +1s:*
Gosling Von (vongosl...@apache.org)
ShannonDing(ding...@apache.org)
Du Heng(duhengfore...@apache.org)
Justin Mclean(jus...@classsoftware.com)


*Non-binding votes +1s:*
Jin Rongtong(jinrongt...@apache.org)


The release will be published soon.


Thanks,
The Apache RocketMQ Team

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

[ShannonDing]

Hi,
+1(binding)
As the release manager, I checked the RC1 following the checklist.
And any other check point is welcomed and please feel free to reply to this 
email, I sincerely hope to your feedback.
On 03/23/2020 22:31，ShannonDing wrote：



Hello RocketMQ Community,

This is the vote for version 2.1.0 of Apache RocketMQ Client CPP.

This release is a major upgrade, mainly including message tracing for pub and 
sub and support for higher version of GCC and add asan/lsan to check memories. 
The stability of the core is further improved.

The artifacts:

https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/2.1.0-rc1/

Git tag for the release:

https://github.com/apache/rocketmq-client-cpp/releases/tag/2.1.0

Hash for the release tag:

aee285fa1948d15cc1c6a70109a151bd044bc51a

Release Notes:

http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-2.1.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

[VOTE]Release Apache RocketMQ Client CPP 2.1.0 RC1.

[ShannonDing]

Hello RocketMQ Community,

This is the vote for version 2.1.0 of Apache RocketMQ Client CPP.

This release is a major upgrade, mainly including message tracing for pub and 
sub and support for higher version of GCC and add asan/lsan to check memories. 
The stability of the core is further improved.

The artifacts:

https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/2.1.0-rc1/

Git tag for the release:

https://github.com/apache/rocketmq-client-cpp/releases/tag/2.1.0

Hash for the release tag:

aee285fa1948d15cc1c6a70109a151bd044bc51a

Release Notes:

http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-2.1.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 4.7.0 RC1

[ShannonDing]

+1,
check list:

[ 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 03/9/2020 17:14，heng du wrote：
+1, binding

verified:
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.
Start nameserver and broker according to the quick-start
Run clusterList command to see if the version is correct

Also verified:
master-slave replication with SYNC_MASTER model

Rongtong Jin  于2020年3月5日周四 下午9:18写道：

Hello RocketMQ Community,

This is the vote for 4.7.0 of Apache RocketMQ.

This release optimized synchronous replication and greatly improved
synchronous replication performance. This release made some enhancements,
such as exception handle of transaction check service, preventing the
client from committing too frequently, etc. This release also fixed some
issues about mqadmin tools, message id setting, etc.

The artifacts:
https://dist.apache.org/repos/dist/dev/rocketmq/4.7.0-rc1/

The staging repo:
https://repository.apache.org/content/repositories/orgapacherocketmq-1044

Git tag for the release:
https://github.com/apache/rocketmq/tree/release-4.7.0

Hash for the release tag:
8ef01a6c635f6972847c40d5540b1945180d7cbd

Release Notes:
https://rocketmq.apache.org/release_notes/release-notes-4.7.0/

The artifacts have been signed with Key :
D606079AF789227A1F39928A02C8C9527DDD1959, 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.
[]  Start nameserver and broker according to the quick-start
[]  Run clusterList command to see if the version is correct

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

[DISCUSS]Release Apache rocketmq-client-cpp 2.0.1

[ShannonDing]

Hello RocketMQ Community,




Apache RocketMQ team is about to release Apache rocketmq-client-cpp 2.0.1 and 
we will stop merge PR.

 If your PR has not been merged and needs further attention, please reply to 
this email and we will review it as soon as possible.




Best Regards,

Apache RocketMQ Team.

[ANNOUNCE] Release Apache RocketMQ Client CPP 2.0.0

[ShannonDing]

Hello RocketMQ Community,




The Apache RocketMQ team would like to announce the release of Apache RocketMQ 
Client CPP 2.0.0

This release is a major upgrade, mainly including native support for namespace 
Settings and support for the v2 version of the RocketMQ protocol. The stability 
of the core is further improved.

The release artifacts can be downloaded here:

http://mirror.bit.edu.cn/apache/rocketmq/rocketmq-client-cpp/2.0.0/rocketmq-client-cpp-2.0.0-bin-release.tar.gz

http://mirror.bit.edu.cn/apache/rocketmq/rocketmq-client-cpp/2.0.0/rocketmq-client-cpp-2.0.0-source-release.tar.gz

The release notes can be found here:

http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-2.0.0/




Thanks,

The Apache RocketMQ Team

[RESULT][RESTART][VOTE]Release Apache RocketMQ Client CPP 2.0.0 RC1.

[ShannonDing]

Hello RocketMQ Community,




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




*Binding votes +1s:*

Gosling Von (vongosl...@apache.org)

ShannonDing(ding...@apache.org)

Du Heng(duhengfore...@apache.org)




*Non-binding votes +1s:*

Jin Rongtong(jinrongt...@apache.org)




The release will be published soon.




Thanks,

The Apache RocketMQ Team

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

[ShannonDing]

+1
as the release manager, I have checked the issues:

[ 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.



On 02/19/2020 09:44，heng du wrote：
+1 (binding)

I checked:
-  checksums and signatures
- LICENSE and NOTICE looks OK
- release note
- Hash and Tag in Github


Rongtong Jin  于2020年2月18日周二 下午11:15写道：

+1(non-binding)

I cheked：
Checksums and PGP signatures are valid for Source package.
Checksums and PGP signatures are valid for Binary package.
No compiled archives bundled in source archive.
Hash and Tag in GitHub repo is matching the current artifacts.
License and Notice are correct in source package.

ShannonDing 写道：
Hello RocketMQ Community,

This is the vote for version 2.0.0 of Apache RocketMQ Client CPP.

This release is a major upgrade, mainly including native support for
namespace Settings and support for the v2 version of the RocketMQ protocol.
The stability of the core is further improved.

The artifacts:


https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-client-cpp/2.0.0-rc1/

Git tag for the release:

https://github.com/apache/rocketmq-client-cpp/releases/tag/2.0.0

Hash for the release tag:

91c18422ec5a200b53da4c33226fa9117db64fe4

Release Notes:


http://rocketmq.apache.org/release_notes/release-notes-rocketmq-client-cpp-2.0.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