[
https://issues.apache.org/jira/browse/KAFKA-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192779#comment-16192779
]
Sönke Liebau commented on KAFKA-5637:
-------------------------------------
Apologies for letting this slide for so long, I had a medical emergency in the
family and became a father somewhat earlier than anticipated, so am still
trying to get back into the groove so to say. I will pick this up in the next
two weeks and submit an initial proposal, so it can hopefully go into the first
bugfix release.
> 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.1.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)
