You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@rocketmq.apache.org by zhibo li <os...@gmail.com> on 2022/09/19 08:09:16 UTC
[DISCUSS] Prepare to release Apache RocketMQ 4.9.5
Hello RocketMQ Community,
This is the discussion for the release of Apache RocketMQ 4.9.5 Release.
In this release, upgrading DLeger to version 0.2.7 enhances performance. Also,
some bugs have been fixed involving ACL, Namesrv auto discovery, consumer
offset persist, and so on.
Welcome everyone to comment in this email, and if no other sounds, I would
like to call for a vote for this release :-)
Regards，
Lizhibo
Re:Re: [DISCUSS] Prepare to release Apache RocketMQ 4.9.5
Posted by jinrongtong <ji...@apache.org>.
Hi, erveryone
If there is any other pull requests that need to be merged to version 4.9.5 plz reply this email.
At 2022-09-20 21:05:32, "Xinyu Zhou" <yu...@apache.org> wrote:
>+1 for holding the release of 4.9.5, give a chance for issue 3905:
>https://github.com/apache/rocketmq/issues/3905
>
>It's important to bring the brokerName fields back to 4.9.x LTS version.
>
>Also, please speed up closing this issue, thanks drpmma.
>
>Regards,
>Xinyu Zhou
>
>On Tue, Sep 20, 2022 at 2:30 PM Zhouxiang Zhan <zh...@gmail.com> wrote:
>
>> Hi. There's an issue <https://github.com/apache/rocketmq/issues/3905>
>> about
>> the implementation of brokerName field in the remoting command protocol
>> proposed to be backported to 4.9.5, which is already implemented in the 5.0
>> version.
>>
>> On Mon, Sep 19, 2022 at 4:10 PM zhibo li <os...@gmail.com> wrote:
>>
>> > Hello RocketMQ Community,
>> >
>> >
>> > This is the discussion for the release of Apache RocketMQ 4.9.5 Release.
>> >
>> >
>> > In this release, upgrading DLeger to version 0.2.7 enhances performance.
>> > Also,
>> > some bugs have been fixed involving ACL, Namesrv auto discovery, consumer
>> > offset persist, and so on.
>> >
>> >
>> >
>> >
>> >
>> > Welcome everyone to comment in this email, and if no other sounds, I
>> would
>> > like to call for a vote for this release :-)
>> >
>> >
>> > Regards，
>> >
>> > Lizhibo
>> >
>>
Re: [DISCUSS] Prepare to release Apache RocketMQ 4.9.5
Posted by Xinyu Zhou <yu...@apache.org>.
+1 for holding the release of 4.9.5, give a chance for issue 3905:
https://github.com/apache/rocketmq/issues/3905
It's important to bring the brokerName fields back to 4.9.x LTS version.
Also, please speed up closing this issue, thanks drpmma.
Regards,
Xinyu Zhou
On Tue, Sep 20, 2022 at 2:30 PM Zhouxiang Zhan <zh...@gmail.com> wrote:
> Hi. There's an issue <https://github.com/apache/rocketmq/issues/3905>
> about
> the implementation of brokerName field in the remoting command protocol
> proposed to be backported to 4.9.5, which is already implemented in the 5.0
> version.
>
> On Mon, Sep 19, 2022 at 4:10 PM zhibo li <os...@gmail.com> wrote:
>
> > Hello RocketMQ Community,
> >
> >
> > This is the discussion for the release of Apache RocketMQ 4.9.5 Release.
> >
> >
> > In this release, upgrading DLeger to version 0.2.7 enhances performance.
> > Also,
> > some bugs have been fixed involving ACL, Namesrv auto discovery, consumer
> > offset persist, and so on.
> >
> >
> >
> >
> >
> > Welcome everyone to comment in this email, and if no other sounds, I
> would
> > like to call for a vote for this release :-)
> >
> >
> > Regards，
> >
> > Lizhibo
> >
>
Re: [DISCUSS] Prepare to release Apache RocketMQ 4.9.5
Posted by Zhouxiang Zhan <zh...@gmail.com>.
Hi. There's an issue <https://github.com/apache/rocketmq/issues/3905> about
the implementation of brokerName field in the remoting command protocol
proposed to be backported to 4.9.5, which is already implemented in the 5.0
version.
On Mon, Sep 19, 2022 at 4:10 PM zhibo li <os...@gmail.com> wrote:
> Hello RocketMQ Community,
>
>
> This is the discussion for the release of Apache RocketMQ 4.9.5 Release.
>
>
> In this release, upgrading DLeger to version 0.2.7 enhances performance.
> Also,
> some bugs have been fixed involving ACL, Namesrv auto discovery, consumer
> offset persist, and so on.
>
>
>
>
>
> Welcome everyone to comment in this email, and if no other sounds, I would
> like to call for a vote for this release :-)
>
>
> Regards，
>
> Lizhibo
>