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 soon, but changes made now need some
special consideration anyway since Kafka releases up to now haven't made
any compatibility guarantees. Semantic versioning is probably a good
baseline, but even the choice of 0.8.3 vs. 0.9.0 for our next release is
pretty arbitrary since Kafka has so far made breaking changes even in minor
releases.
Until we resolve the more general compatibility rules, I'd suggest we let
this particular issue progress with the basic approach of providing one
minor point release of compatibility -- guarantee compatibility with the
previous interface for one release, providing a window for transition, then
removing the functionality in the subsequent release. For now, this just
means adding the JIRA to 0.9.x that removes the functionality, and if we
decide on a different policy, we can just adjust the Fix Version for the
removal of the old tool.
-Ewen
On Thu, Jul 2, 2015 at 12:19 AM, Jaikiran Pai <jai.forums2...@gmail.com>
wrote:
> 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
> instead?
>
> -Jaikiran
>
> On Thursday 02 July 2015 06:27 AM, Ashish Singh wrote:
>
>> 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.apache.org/confluence/pages/viewpage.action?pageId=56852556
>> }
>> accordingly. {KAFKA-2307}(
>> https://issues.apache.org/jira/browse/KAFKA-2307)
>> is to remind up that we need to drop the tool in 0.9.1.
>>
>> Let me know if I am missing out on any step that we decided on for the
>> deprecation.
>>
>>
>
--
Thanks,
Ewen
