As you know the Incubator level vote of the release is failed due to a
licensing issue.
The issue is fixed and the license problem is solved, it's in Patch
Available state:
https://issues.apache.org/jira/browse/RATIS-249
After it's merged we can start a new vote thread.
Marton
ps: I
a release?
>
> Tsz-Wo
>
> On Mon, Apr 23, 2018 at 3:46 AM, Marton, Elek <e...@apache.org> wrote:
>> Quick update:
>>
>>
>> TLDR; We need RATIS-227/RATIS-228 (and imho RATIS-229) for the 0.2.0
>> release.
>&
the issues. All RATIS-227, RATIS-228 and
RATIS-229 are new resolved and there are no more blockers. Let's roll
a release?
Tsz-Wo
On Mon, Apr 23, 2018 at 3:46 AM, Marton, Elek <e...@apache.org> wrote:
Quick update:
TLDR; We need RATIS-227/RATIS-228 (and imho RATIS-229) for the 0.2.0
r
ATIS-228 (and imho RATIS-229) for the 0.2.0
> release.
>
>
>
> Current Blocker/Patch Available jiras:
>
> BLOCKER:
>
> RATIS-227 TestRaftWithGrpc.testBasicAppendEntriesWithAllReplication fails
> --> No patch, yet
>
> RATIS-228 Handle zero size log_inp
Quick update:
TLDR; We need RATIS-227/RATIS-228 (and imho RATIS-229) for the 0.2.0
release.
Current Blocker/Patch Available jiras:
BLOCKER:
RATIS-227 TestRaftWithGrpc.testBasicAppendEntriesWithAllReplication fails
--> No patch, yet
RATIS-228 Handle zero size log_inprogress f
Hi,
I would like to restart the discussion about a ratis release.
1. It's hard to find the right time to release as thanks to the
continuous testing with hdfs/ozone we always have some minor
issues/improvements.
I would suggest to do a release as soon as possible and do more frequent