Re:Re: [VOTE] Release gRPC Java Client for Apache RocketMQ 5.0.7

[caigy]

+1 I've 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




在 2024-06-13 17:07:20，"沈林" <2011shen...@gmail.com> 写道：
>+1
>I have checked all of the four items.
>
>lollipop  于2024年6月13日周四 15:36写道：
>
>> +1
>> I have checked all of the four items.
>>
>> On Wed, Jun 12, 2024 at 5:27 PM zhimin li  wrote:
>>
>> > Hello RocketMQ Community,
>> >
>> > This is the vote for gRPC Java Client for Apache RocketMQ 5.0.7.
>> >
>> > Apache RocketMQ gRPC clients 5.x series follow the specs of rocketmq-apis
>> > ;, and are built on top of
>> > Protocol
>> > Buffer and gRPC.
>> >
>> > The artifact url:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-clients/rocketmq-client-java/5.0.7-rc1/
>> >
>> > The staging repo for maven:
>> >
>> https://repository.apache.org/content/repositories/orgapacherocketmq-1327/
>> >
>> > Git tag for the release:
>> > https://github.com/apache/rocketmq-clients/releases/tag/java-5.0.7
>> >
>> > Hash for the release tag:
>> > db74fa880ea9c10d46a4be8659caa51ca1259734
>> >
>> > The artifact have been signed with
>> > Key: C9D394D2, 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
>> >
>> > 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-66]Support KV(Rocksdb) Storage

[caigy]

+1

在 2023-07-21 09:35:14，"fan wang"  写道：
>+1
>
>The link to the proposal is followed by an additional "" suffix, by
>the way.
>
>jinrongtong  于2023年7月20日周四 16:18写道：
>
>> +1
>> At 2023-07-20 16:15:30, "Qingshan Lin"  wrote:
>> >+1
>> >
>> >On 2023/07/20 02:24:42 闽 wrote:
>> >> Hi, RocketMQ Community,
>> >>
>> >>
>> >> As discussed in the previous email, we launched a new RIP 66 to support
>> KV(Rocksdb) storage. Now the shepherds@gongyi-zmp
>> and@hill007299are 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!
>> >> Fujian Zhao
>> >>
>> >>
>> >> English proposal:
>> https://docs.google.com/document/d/e/2PACX-1vT3QJ8XDbKi8HQKaIDodOD4vIV0-xlERFtg8Ed3FsYUi7IfRs5JVKjElGaxpk-0ErH0xdWT0Vv-a1u5/pub
>> ;
>> >>
>> >>
>> >>
>> >> left
>> >> 2573259...@qq.com
>> >>
>> >>
>> >>
>> >> 
>>

Re:[VOTE] Release Apache RocketMQ 4.9.7 RC1

[caigy]

+1 (Non-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]  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 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][RIP-62]Coldreadcontrol

[caigy]

+1






在 2023-03-07 14:55:05，"2017赵科" <464473...@qq.com.INVALID> 写道：
>Hi, RocketMQ Community,
>
>
>As discussed in the previous email, we launched a new RIP[RIP-62] Cold read 
>control to support this feature. Now thei...@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

[caigy]

+1 （Non-binding）

I checked:

[OK]  Checksums and PGP signatures are valid for source package.
[OK]  Source code artifacts have correct names matching the current release.
[OK]  License and Notice are correct in source package.
[OK]  All files have license headers in source package if necessary.
[OK]  No compiled archives bundled in source archive.
[OK]  Hash and Tag in GitHub repo are matching the current artifacts.
[OK]  The code can be built success in the source package.






At 2023-02-06 15:13:43, "jinrongtong"  wrote:
>Hi All, the correct release notes is 
>https://rocketmq.apache.org/release-notes/2023/02/06/release-notes-rocketmq-spring-2.2.3
>
>
>
>At 2023-02-06 13:36:43, "jinrongtong"  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

[caigy]

+1. I checked:

[Y]  run check LICENSE, should be Apache V2

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

[Y]  verify the asc(PGP sign),SHA512

[Y] build the source successfully



在 2023-01-06 14:57:13，"fuyou"  写道：
>+1
>
>nize  于2023年1月6日周五 14:09写道：
>
>> 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
>>
>
>
>-- 
>   =
>
>  fuyou001
>Best Regards

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

[caigy]

+1





在 2022-12-05 19:37:51，"hzh0425"  写道：
>+1
>
>
>
>| |
>hzh...@163.com
>|
>|
>邮箱：hzh...@163.com
>|
>
>
>
>
> 回复的原邮件 
>| 发件人 | nize |
>| 日期 | 2022年12月05日 17:40 |
>| 收件人 | dev@rocketmq.apache.org |
>| 抄送至 | |
>| 主题 | [VOTE][RIP-58]RocketMQ Streams improvement |
>Hi, RocketMQ Community,
>
>As discussed in the previous email, we launched a new RIP to  start it. Now
>the shepherds @ShannonDing 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:Re: [VOTE][RIP-41]Build rocketmq e2e test and github action cicd

[caigy]

+1, it helps improve product quality of RocketMQ




--

Gaoyang Cai




在 2022-05-05 10:51:12，"heng du"  写道：
>+1
>
>YuanchenZhang  于2022年5月5日周四 10:46写道：
>
>> 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/
>>
>>
>>

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

[caigy]

+1






在 2022-04-15 10:26:45，"heng du"  写道：
>+1
>
>孙先生  于2022年4月15日周五 10:23写道：
>
>> 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:Re:Re: [VOTE] Release Apache RocketMQ Streams 1.0.1-preview RC1

[caigy]

+1
I checked: 
[ok]  The checksum for release package is correct.
[ok]  Source code artifacts have correct names matching the current release.
[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.
[ok]  Maven rat check passed.

在 2022-04-16 11:38:30，"jinrongtong"  写道：
>+ 1, I Checked 
>
>
>[ok] Hash and Tag in GitHub repo are matching the current artifacts.
>
>[ok] The code can be built success in the source package.
>
>[ok] The maven staging repo is ok
>
>[ok] The release manager's KEY in RocketMQ KEYS file is ok
>
>
>At 2022-04-15 16:55:15, "zhibo li"  wrote:
>>+1
>>
>>zhibo li  于2022年4月13日周三 10:13写道：
>>
>>> Hello RocketMQ Community,
>>>
>>>
>>>
>>> This is the vote for the 1.0.1-preview release of Apache RocketMQ-Streams.
>>>
>>>
>>> The artifacts:
>>>
>>>
>>> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-streams/1.0.1-preview-rc1/
>>> 
>>>
>>>
>>> The staging repo:
>>>
>>> https://repository.apache.org/content/repositories/orgapacherocketmq-1085
>>>
>>>
>>> Git tag for the release:
>>>
>>>
>>> https://github.com/apache/rocketmq-streams/releases/tag/rocketmq-streams-1.0.1-preview
>>>
>>>
>>> Hash for the release tag:
>>>
>>> 5e3ffb2ddda8234928006086f711b051a29657f6
>>>
>>>
>>> Release Notes:
>>>
>>>
>>> http://rocketmq.apache.org/release_notes/release-notes-rocketmq-streams-1.0.0-preview/
>>>
>>>
>>> The artifacts have been signed with Key :
>>>
>>> 5F4943FC0449417C342D70B4AA685CA96FF11BAF, 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.3 RC1

[caigy]

+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] Creating an external logappender repository

[caigy]

+1

在 2022-02-08 17:37:26，"dongeforever"  写道：
>+1
>
>Rongtong Jin  于2022年2月8日周二 17:35写道：
>
>> +1
>>
>> 倪泽 uncleran...@gmail.com写道：
>> > +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
>> > > > >
>> > > > >
>> > > >
>> > >
>>

[VOTE][RIP-25] Ease of Use Improvements on RocketMQ Client API

[caigy]

Hi, RocketMQ Community, 

As discussed in the previous email, we launched a new RIP to improve ease of 
use for RocketMQ Client. Now the shepherds @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!

links:https://docs.google.com/document/d/1hlwEe6jcqafEMQIiOp-dLirDad6fa7dpajAdw0JAWNs/edit?usp=sharing

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

[caigy]

As rocketmq-logappender only provides appenders to log to RocketMQ, but 
RocketMQ itself doesn't depend on it, I think it would be more appropriate to 
put it in rocketmq-externals.


在 2021-12-16 22:18:04，"heng du"  写道：
>Dear community,
>
>Today I would like to kickstart a series of discussions around creating an
>external logappender[1] repository. , and maybe It is recommended to put it
>in 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.
>
>Now I’d first like to collect your viewpoints on this discussion, please
>feel free to reply to this email if you have any other points.
>
>
>[1] https://github.com/apache/rocketmq/tree/master/logappender
>[2] https://github.com/apache/rocketmq-externals
>
>Thanks
>Henry
>
>
>heng du  于2021年12月16日周四 22:17写道：
>
>> Dear community,
>>
>> Today I would like to kickstart a series of discussions around creating an
>> external logappender[1] repository. , and maybe It is recommended to put
>> it in 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.
>>
>> Now I’d first like to collect your viewpoints on this discussion, please
>> feel free to reply to this email if you have any other points.
>>
>> Thanks
>> Henry
>>

[DISCUSS] RIP-25 Ease of Use Improvements on RocketMQ Client API

[caigy]

RIP-25 Ease of Use Improvements on RocketMQ Client API


  * Current Status: Draft  
  * Authors: caigy https://github.com/caigy
  * Shepherds: duhengforever duhengfore...@apache.org  
  * Mailing List discussion: dev@rocketmq.apache.org 
  * Pull Request: #PR_NUMBER  
  * 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? No. 


Why should we do that
 * Are there any problems of our current project?
Currently, RocketMQ's client API is a bit complex, and there exists some 
unreasonable encapsulation. For example: 
** There are 20 methods for sending messages in DefaultProducer, with lack 
of encapsulation, which increases complexity in usage.
** DefaultMQPushConsumer provides 10 constructors，which may make user 
difficult to choose one.
** Class Message provides constructors with and without arguments, and also 
provides getters/setters to operate fields of it,  which lacks good separation 
of required and non-required arguments.
API is important media for users to interact with RocketMQ, and it is worth 
investing effort in optimizing its design.

* What can we benefit proposed changes?
Provide clear and easier-to-understand API of RocketMQ, make it easier to 
use, especially for beginners.



Goals


* What problem is this proposal designed to solve?
   Optimize RocketMQ client APIs, including Producer, Consumer and Message, 
remove unnecessary APIs, and provide better encapsulation. Current unreasonable 
APIs will be marked deprecated and will be removed in the future. After this 
optimization, the APIs should keep as stable as possible.

* To what degree should we solve the problem?
We wish developers can use RocketMQ more easily with new APIs.


Non-Goals


* What problem is this proposal NOT designed to solve?
   This proposal will NOT change feature and performance.

* Are there any limits of this proposal?
  Nothing specific.



Changes


* Architecture
 No architecture changes in this proposal.

* Interface Design/Change
   ** Method signature changes. Yes. 
   For example: 
   *** Add generic to support data type of message body in Message.
   *** Support chain-call instantiation of Producer, Consumer, Message, 
eg：Message.builder().topic("msg  topic").body("msg body").build();
   *** Producer provides unified and stable send() API, which is like 
write() method of UNIX file I/O.
   *** Add asynchronous message consumption API based on CompletableFuture 
in Consumer. 
   *** etc...

   ** Method behavior changes. No.  CLI command changes. No. 
   ** Log format or content changes. No.

* Compatibility, Deprecation, and Migration Plan
   ** Are backward and forward compatibility taken into consideration?
  Optimized APIs should NOT affect compatibility, some APIs would be marked 
deprecated. New features will use optimized APIs, encouraging users not to use 
deprecated APIs.
 
   ** Are there deprecated APIs?
  Yes. Some unreasonable APIs will be deprecated in this RIP.  

  ** How do we do migration?
  Unreasonable APIs are marked deprecated in this proposal, and will be 
removed in the future.

* Implementation Outline
  We will implement the proposed changes by 1 phase.
  Phase 1
 1. Collect pain points in using RocketMQ client APIs and redesign them. 
 2. Optimize those APIs. 
 3. Mark previous APIs deprecated. 

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

[caigy]

Congrats!

在 2021-09-24 14:48:38，"dongeforever"  写道：
>welcome!
>
>周波  于2021年9月24日周五 下午12:55写道：
>
>> Congrats!
>>
>> 倪泽  于2021年9月24日周五 下午12:36写道：
>>
>> > Congrats !
>> >
>> > Rongtong Jin  于2021年9月24日周五 上午11:42写道：
>> >
>> > > Congrats!
>> > >
>> > > Amber Liu ltambe...@gmail.com写道：
>> > > > Congrats ! well deserved!
>> > > >
>> > > > ShannonDing  于2021年9月24日周五 上午10:41写道：
>> > > >
>> > > > > 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: [VOTE]Release Apache RocketMQ Spring 2.2.1 RC1

[caigy]

+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.>
>发件人: jinrongto...@163.com  代表 jinrongtong 
>
>发送时间: 2021年8月31日 18:56
>收件人: dev@rocketmq.apache.org 
>抄送: us...@rocketmq.apache.org 
>主题: [VOTE]Release Apache RocketMQ Spring 2.2.1 RC1
>
>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:[ANNOUNCE] New committer involved, welcome Xiaofeng Jiang

[caigy]

Congrats!


At 2021-08-30 10:57:08, "heng du"  wrote:
>Hi,
>
>The Project Management Committee (PMC) for Apache RocketMQ has invited
>Xiaofeng Jiang to become a committer and we are pleased
>to announce that he has accepted.
>
>Being a committer enables easier contribution to the project since there is
>no need to go via the patch submission process. This should enable better
>productivity.
>
>
>Yours,
>Apache RocketMQ PMC

Re:[ANNOUNCE] New committer involved, welcome Jidi Zhang

[caigy]

Congrats!

At 2021-08-30 10:58:37, "heng du"  wrote:
>Hi,
>
>The Project Management Committee (PMC) for Apache RocketMQ has invited
>Jidi Zhang to become a committer and we are pleased to announce that he has
>accepted.
>
>Being a committer enables easier contribution to the project since there is
>no need to go via the patch submission process. This should enable better
>productivity.
>
>
>Yours,
>Apache RocketMQ PMC

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

[caigy]

I vote +1 (non-binding)




I checked the following:

- Licence by Apache RAT

- Hashes of binary and source files are correct

- Signatures of binary and source files are correct

- Source code can be built successfully and all unit tests are passed locally
- Nameserver and Broker can be run successfully and mqadmin clusterList command 
responds correct cluster message