[
https://issues.apache.org/jira/browse/KAFKA-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264455#comment-15264455
]
ASF GitHub Bot commented on KAFKA-1880:
---------------------------------------
GitHub user granthenke opened a pull request:
https://github.com/apache/kafka/pull/1291
WIP - KAFKA-1880: Add support for checking binary/source compatibility
This is a WIP pull request to show how I am generating the reports attached
to the Jira. I am putting it up now so that we understand what has been
changed/broken before the 0.10 release.
At some point we may want to leverage something like this to break the
build too, but I think generating a report is a good start.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/granthenke/kafka api-check
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1291.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1291
----
commit 5af41e2ab52bb62a4bf9d13d516b4d2789e357da
Author: Grant Henke <[email protected]>
Date: 2016-04-29T18:00:39Z
WIP - KAFKA-1880: Add support for checking binary/source compatibility
----
> Add support for checking binary/source compatibility
> ----------------------------------------------------
>
> Key: KAFKA-1880
> URL: https://issues.apache.org/jira/browse/KAFKA-1880
> Project: Kafka
> Issue Type: New Feature
> Reporter: Ashish K Singh
> Assignee: Grant Henke
> Attachments: compatibilityReport-only-incompatible.html,
> compatibilityReport.html
>
>
> Recent discussions around compatibility shows how important compatibility is
> to users. Kafka should leverage a tool to find, report, and avoid
> incompatibility issues in public methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
