Hi Tsz-Wo,
I think using 1.0.2 and 2.4.0 is fine, thanks for the suggestion. Let's wait for grpc 1.48.1 to complete the release before starting the release process for Ratis 2.4.0. Regards, Yaolong Liu At 2022-07-27 23:28:18, "Tsz Wo Sze" <[email protected]> wrote: >Hi Yaolong, > >For ratis-thirdparty, let's make it 1.0.2 since there are not many changes. > >For ratis, I do suggest calling it 2.4.0 instead of 2.3.1 since there are >quite many changes. What do you think? > >Regards, >Tsz-Wo > >On Wed, Jul 27, 2022 at 7:58 AM Yaolong Liu <[email protected]> wrote: > >> Hi Tsz-Wo, >> >> >> Thanks for pointing this out, grpc 1.48.1 seem not be released yet, we can >> wait for it to release and then launch a ratis-thirdparty release. >> The release of Ratis 2.3.1 can be delayed. BTW, should the next version of >> ratis-thirdparty be 1.0.2 or 1.1.0? >> >> >> >> >> Regards, >> Yaolong Liu >> >> >> >> >> >> >> >> >> >> >> >> At 2022-07-27 00:10:53, "Tsz Wo Sze" <[email protected]> wrote: >> >Hi Yaolong, >> > >> >We probably have to update gRPC in ratis-thirdparty due to the recent gRPC >> >"ByteBuffer memory leak in retry mechanism" issue; see >> >https://github.com/grpc/grpc-java/issues/9340 . According to this >> comment >> >https://github.com/grpc/grpc-java/issues/9340#issuecomment-1185995690 , >> they >> >will have a fix in 1.48.1 soon. >> > >> >Tsz-Wo >> > >> > >> >On Tue, Jul 26, 2022 at 8:11 AM Yaolong Liu <[email protected]> wrote: >> > >> >> Hi all, >> >> >> >> >> >> Recently ratis has supported listener and fixed multiple bugs, can we >> >> start the release of 2.3.1? >> >> I want to release based on RATIS-1637 and all previous commits. >> >> If there are any that should or should not appear in 2.3.1, please let >> me >> >> know. >> >> >> >> >> >> Regards, >> >> Yaolong Liu >>
