-1
Version is not correct.
[image: image.png]

heng du <duhengfore...@apache.org> 于2022年3月10日周四 21:44写道:

> +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.
> [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
>
> ShannonDing <ding...@apache.org> 于2022年3月9日周三 10:57写道:
>
>> +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" <jinrongt...@apache.org> 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
>>
>>
>>
>>
>>
>
>

Reply via email to