I agree, I will release ratis 2.0.0 first. Thanks, runzhiwang
Shashikant Banerjee <[email protected]> 于2021年2月2日周二 下午7:33写道： > Let's get ratis 2.0.0 out first. Ratis 1.1 may require some more testing > for stability. > > Thanks @runzhiwang(王杰) <[email protected]> for volunteering for the > same. > > Thanks > Shashi > > On Tue, Feb 2, 2021 at 4:44 PM runzhiwang <[email protected]> wrote: > > > Hi Marton, > > > > Thanks the suggestions, I'm okay to release ratis 2.0.0 first. After > > release 2.0, I will also release ratis 1.1, so that other application, > such > > as Alluxio, can use ratis 1.1. > > > > Thanks, > > runzhiwang > > > > Elek, Marton <[email protected]> 于2021年2月2日周二 下午6:16写道： > > > > > > > > Yesterday we had a long conversation about Ratis release during the > > > Ozone community call [1]: > > > > > > 1. We think that the easiest way to release is Ozone to release Ratis > > > master as Ratis 2.0 (full branch, without cherry-picking) > > > > > > 2. All the new features can be turned off by default (like PRE_VOTE > > > and leader lease). Either by default on Ratis, or just by the Ozone. > > > (follow HDDS-4774) > > > > > > 3. Compatibility will be tested by acceptance tests (thx to Attila we > > > will have a test to test current Ozone with older clients). > > > > > > > > > From this point of view, Ozone needs 2.0 release from master. > > > > > > runzhiwang: you are volunteered to be an RM for 1.1. Do you need a > > > stable 1.1 release, or you would do it for Ozone. > > > > > > If it's for Ozone, can we do 2.0 instead? > > > > > > (I am happy to help in any release which moves us closer to the Ozone > > > release). > > > > > > Thanks, > > > Marton > > > > > > > > > > > > > > > > > > > > > [1]: in the first 30 mins > > > > > > > > > > > > https://cloudera.zoom.us/rec/share/4S9Uf7etdbpwDWDWvnj3J0Af2TnZhbB7ruFavE4T0ucLKinclxa7x87dBZdYjgUE.HIacLrBnWPsnNmaZ > > > > > > Passcode: $PS1wQ.N > > > > > >
