It does make sense, thanks for the clarification. If we deprecate the producer first, does it mean that the following release won't have a scala producer but will have a scala consumer? Actually I should have asked this question first: what's the deprecation path precisely?
-Flavio > On 23 Feb 2016, at 17:28, Ismael Juma <ism...@juma.me.uk> wrote: > > Hi Flavio, > > On Tue, Feb 23, 2016 at 9:23 AM, Flavio Junqueira <f...@apache.org> wrote: > >> Ismael, I'm curious about why you want to deprecate one and not the other. >> You say that it is premature to deprecate the old scala consumers and I'm >> wondering about the reasoning behind it. >> > > The new Java producer was introduced in 0.8.2 and it's considered > production-ready. The new Java consumer was introduced in 0.9.0.0 and it's > still marked as beta. We would like to have at least one full release cycle > where the new consumer is no longer in beta, before we consider deprecating > the old consumers. Does that make sense? > > Ismael
