Thanks for explaining, Ewen.
-Jaikiran
On Thursday 02 July 2015 02:03 PM, Ewen Cheslack-Postava wrote:
Jaikiran,
After the last KIP discussion, I've been tasked with proposing a policy to
address general rules across all public interfaces including APIs, configs,
metrics, and command line inter
Jaikiran,
After the last KIP discussion, I've been tasked with proposing a policy to
address general rules across all public interfaces including APIs, configs,
metrics, and command line interfaces, but haven't had a chance to send out
a concrete proposal yet.
I'll send that out to the dev list s
Just curious about deprecation policy and the version schemes. Consider
a certain feature was deprecated in 0.9.2, so a WARN gets logged in that
version. Does that now mean a (bug fix release) 0.9.3 will drop that
feature? Shouldn't the dropping of the feature be done in a 0.10.0
release instea
Hey Guys,
In last KIP hangout, we decided on following path for deprecating
ConsumerOffsetChecker.
1. Add deprecation warning to the tool for one release. In this case, the
warning will be added in 0.9.0.
2. Drop it completely in next release, 0.9.1.
I have updated the (KIP-23){
https://cwiki.ap
