Re: Release 2.4.0 - Feature Freeze

Sorry for my confusion, I thought the intention was listing both, wip and done features. > Let's bring the discussion back to the list of features to be included in 2.4.0 Do we want to include #4062 in 2.4.0? I'm very interested in this one. Congrats

Re: Release 2.4.0 - Feature Freeze

On Wed, Apr 24, 2019 at 1:51 AM Matteo Merli wrote: > > I don't think the original email was trying to list all the features. It > > was trying to bring up all the *in-progress* features > > to discuss > > I don't really want to drag the conversation but I think it difficult > to characterize the

Re: Release 2.4.0 - Feature Freeze

> I don't think the original email was trying to list all the features. It > was trying to bring up all the *in-progress* features > to discuss I don't really want to drag the conversation but I think it difficult to characterize the unilaterally declaration of a "feature freeze immediate now" for

Re: Release 2.4.0 - Feature Freeze

Hi Lovelle, I don't think the original email was trying to list all the features. It was trying to bring up all the *in-progress* features to discuss, so that the community can wrap up the tasks for the release manager to release 2.4.0. If an in-progress feature that is not needed for 2.4.0, peopl

Re: Release 2.4.0 - Feature Freeze

Hi! My 2 cents, as Matteo said, the feature which is worth mentioning is negative ack instead of its interceptor. Idk If it's as a relevant feature, but in pull #4031 we've just finish adding support for seek() in Reader impl. -- *Ezequiel Lovelle*