[
https://issues.apache.org/jira/browse/KAFKA-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108724#comment-16108724
]
Tom Bentley commented on KAFKA-5637:
------------------------------------
I'd be interested to know what the expectation is for APIs to be binary
compatible vs. source compatible. In particular, if an API is annotated as
stable then must changes be binary compatible? If so, how do we propose to
verify this? Do the rules differ for unstable APIs?
> Document compatibility and release policies
> -------------------------------------------
>
> Key: KAFKA-5637
> URL: https://issues.apache.org/jira/browse/KAFKA-5637
> Project: Kafka
> Issue Type: Improvement
> Components: documentation
> Reporter: Ismael Juma
> Assignee: Sönke Liebau
> Fix For: 1.0.0
>
>
> We should document our compatibility and release policies in one place so
> that people have the correct expectations. This is generally important, but
> more so now that we are releasing 1.0.0.
> I extracted the following topics from the mailing list thread as the ones
> that should be documented as a minimum:
> *Code stability*
> * Explanation of stability annotations and their implications
> * Explanation of what public apis are
> * *Discussion point: * Do we want to keep the _unstable_ annotation or is
> _evolving_ sufficient going forward?
> *Support duration*
> * How long are versions supported?
> * How far are bugfixes backported?
> * How far are security fixes backported?
> * How long are protocol versions supported by subsequent code versions?
> * How long are older clients supported?
> * How long are older brokers supported?
> I will create an initial pull request to add a section to the documentation
> as basis for further discussion.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
