Hi Tom, good question.
Due to the new version policies, the deprecation will be in the coming 1.0.0 release but then, due to a breaking change on the API, the removal should be on 2.0.0 I guess. Thanks, Paolo Patierno Senior Software Engineer (IoT) @ Red Hat Microsoft MVP on Windows Embedded & IoT Microsoft Azure Advisor Twitter : @ppatierno<http://twitter.com/ppatierno> Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno> Blog : DevExperience<http://paolopatierno.wordpress.com/> ________________________________ From: Tom Bentley <t.j.bent...@gmail.com> Sent: Tuesday, August 8, 2017 11:00 AM To: dev@kafka.apache.org Subject: Re: [VOTE] KIP-176 : Remove deprecated new-consumer option for tools The KIP is here for any one, like me, who hasn't seen it yet: https://cwiki.apache.org/confluence/display/KAFKA/KIP-176:+Remove+deprecated+new-consumer+option+for+tools Paolo, the KIP says "On the next release cycle we could totally remove the option." Exactly which release are you proposing that be? Thanks, Tom On 8 August 2017 at 11:53, Paolo Patierno <ppatie...@live.com> wrote: > Hi devs, > > > I didn't see any more comments about this KIP. The JIRAs related to the > first step (so making --new-consumer as deprecated with warning messages) > are merged. > > I'd like to start a vote for this KIP. > > > Thanks, > > > Paolo Patierno > Senior Software Engineer (IoT) @ Red Hat > Microsoft MVP on Windows Embedded & IoT > Microsoft Azure Advisor > > Twitter : @ppatierno<http://twitter.com/ppatierno> > Linkedin : paolopatierno<http://it.linkedin.com/in/paolopatierno> > Blog : DevExperience<http://paolopatierno.wordpress.com/> >
