+1

jinrongtong <jinrongt...@apache.org> 于2023年2月24日周五 18:06写道:

> +1, I Checked<br/>[OK]  verify the asc(PGP sign),SHA512<br/>[OK]  maven
> jar in nexus repo is right<br/>[OK] Hash and Tag in GitHub repo is matching
> the current artifacts<br/><br/>In addition, it would be better to update
> year to 2023 in source package's notice file in next release.
> At 2023-02-24 15:02:45, "Qingshan Lin" <linh...@apache.org> wrote:
> >good job. The capabilities of MQTT are getting richer。
> >+1
> >
> >On 2023/02/24 03:29:08 Ping Wang wrote:
> >> Hello RocketMQ Community,
> >>
> >> This is the vote for 1.0.1 of Apache RocketMQ-MQTT.
> >>
> >> This version adds support for the two features WILL and RETAIN, and
> >> introduces the META module.
> >>
> >> The artifacts:
> >> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-mqtt/
> >>
> >> The staging repo:
> >>
> https://repository.apache.org/content/repositories/orgapacherocketmq-1133/
> >>
> >> Git tag for the release:
> >>
> https://github.com/apache/rocketmq-mqtt/releases/tag/rocketmq-mqtt-1.0.1
> >>
> >> Hash for the release tag:
> >> 9eefd0901454e3fbf36344e0f725b8d28f65e26f
> >>
> >> The artifacts have been signed with Key :
> >> D8B0E224FC82CC6782B7F09FEFAD557E48236FB9, 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
> >>
> >> 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
> >>
>


-- 
Thanks,
Xin

Reply via email to