K, give me a heads up when you think it is time...
Gary
On Tue, Aug 1, 2023, 7:19 PM Alex Herbert wrote:
> On Tue, 1 Aug 2023 at 14:31, Gary Gregory wrote:
> >
> > That all sounds good.
> >
> > Do you all feel the API will be stable and final enough for a 4.5.0
> release
> > or that we should
On Tue, 1 Aug 2023 at 14:31, Gary Gregory wrote:
>
> That all sounds good.
>
> Do you all feel the API will be stable and final enough for a 4.5.0 release
> or that we should release a milestone 4.5.0-M1 first?
Given the frequency of changes that are still taking place I don't
think it wise to
That all sounds good.
Do you all feel the API will be stable and final enough for a 4.5.0 release
or that we should release a milestone 4.5.0-M1 first?
Gary
On Tue, Aug 1, 2023, 9:26 AM Claude Warren wrote:
> There are currently 3 planned Bloom filter changes. The first is [1], the
> second
There are currently 3 planned Bloom filter changes. The first is [1], the
second [2] is waiting for 1 to land before being completed, and the final
one is a Stable bloom filter implementation [3] is waiting for the second
to land to reduce the size of the change.
[1]
The tests have to cover both deprecated and current APIs.
Gary
On Mon, Jul 31, 2023, 12:18 PM Sruteesh Kumar
wrote:
> But all the test cases are following deprecated OptionBuilder class right?
> optionalArg is handled differently in OptionBuilder and Option.builder()
> and that's where I got
