Hi Tsz-Wo,

I'll finish RATIS-1612 in the near future, 
it's not that urgent right now, so I think we can hold off on finishing the 
2.3.1 release.


Regards.
Yaolong Liu














At 2022-07-07 03:27:40, "Tsz Wo Sze" <[email protected]> wrote:
>Also, if we are not in a hurry, we should also complete
>https://issues.apache.org/jira/browse/RATIS-1612 and include it in 2.3.1.
>Otherwise, the Listener feature is hard to use.
>
>Tsz-Wo
>
>
>On Wed, Jul 6, 2022 at 10:30 AM Tsz Wo Sze <[email protected]> wrote:
>
>> Hi Yaolong,
>>
>> Just found that we have not yet removed the dropwizard dependencies.  We
>> should remove all the dropwizard dependencies and change all the imports to
>> org.apache.ratis.thirdparty.com.codahale.metrics.*; see
>> https://issues.apache.org/jira/browse/RATIS-1601
>>
>> Tsz-Wo
>>
>>
>> On Wed, Jul 6, 2022 at 5:43 AM Yaolong Liu <[email protected]> wrote:
>>
>>> Hi all,
>>>
>>> Ratis Thirdparty 1.0.1 has been released, and Ratis master branch
>>> upgraded to it.  We can proceed with Ratis 2.3.1 release.
>>>
>>> I will release based on branch-2. Since there have been many changes
>>> recently,
>>> I want to release based on RATIS-1614 and all previous commits.
>>> If there are any that should not appear in 2.3.1, please let me know.
>>>
>>>
>>> Regards,
>>> Yaolong Liu
>>>
>>>
>>>
>>>
>>>
>>> At 2022-06-18 17:44:27, "William Song" <[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> and
>>> 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