Hi Tsz-Wo,

I am very willing to serve as the 2.3.1 release manager to help complete this 
task. Since it is my first time participating, I will learn the release process 
first.

Regards,
Yaolong Liu

> 2022年6月20日 下午10:35,Tsz Wo Sze <[email protected]> 写道:
> 
> Sure.  Since it requires committer access to be a release manager, I wonder
> if Yaolong likes to be the 2.3.1 release manager?
> 
> BTW, we should also release ratis-thirdparty 1.0.1 due to
> RATIS-1591 (CVE-2022-24823).
> 
> Tsz-Wo
> 
> On Sun, Jun 19, 2022 at 6:50 PM William Song <[email protected]> wrote:
> 
>> Hi Tsz-Wo,
>> 
>> Thanks! Is there anything we can do to help?
>> 
>>> 2022年6月18日 23:44,Tsz Wo Sze <[email protected]> 写道:
>>> 
>>> Hi William,
>>> 
>>> Since there is a need, we could start preparing the Ratis-2.3.1 release.
>>> Let's first merge the new changes from the master branch to branch-2.
>>> 
>>> Regards,
>>> Tsz-Wo
>>> 
>>> 
>>> 
>>> On Sat, Jun 18, 2022 at 2:44 AM William Song <[email protected]
>> <mailto:[email protected]>> wrote:
>>> 
>>>> Hi all,
>>>> 
>>>> What’s the community’s plan on release Ratis-2.3.1 version? Apache IoTDB
>>>> plan to release a major version 0.14.0 by June 30, while current
>> dependency
>>>> Ratis-2.3.0 have some snapshot bugs that affects the multi-chunk
>> snapshot
>>>> scenario (see https://issues.apache.org/jira/browse/RATIS-1587 <
>>>> https://issues.apache.org/jira/browse/RATIS-1587 <
>> https://issues.apache.org/jira/browse/RATIS-1587>> and
>>>> https://github.com/apache/ratis/pull/655 <
>> https://github.com/apache/ratis/pull/655> <
>>>> https://github.com/apache/ratis/pull/655 <
>> https://github.com/apache/ratis/pull/655>> for detail).
>>>> Therefore, we are hoping that the community can release Ratis-2.3.1
>>>> version and we are happy to help.
>>>> 
>>>> Best Wishes,
>>>> William Song
>> 
>> 

Reply via email to