[
https://issues.apache.org/jira/browse/KAFKA-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694170#comment-14694170
]
ASF GitHub Bot commented on KAFKA-2429:
---------------------------------------
GitHub user ewencp opened a pull request:
https://github.com/apache/kafka/pull/133
KAFKA-2429: Add annotations to mark classes as stable/unstable
This also marks the consumer as unstable to show an example of using these
annotations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ewencp/kafka stability-annotations
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/133.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 #133
----
commit 09c15c37dcd128d608febbb9e578ef0ec85a471d
Author: Ewen Cheslack-Postava <m...@ewencp.org>
Date: 2015-08-12T21:04:01Z
KAFKA-2429: Add annotations to mark classes as stable/unstable
----
> Add annotations to mark classes as stable/unstable
> --------------------------------------------------
>
> Key: KAFKA-2429
> URL: https://issues.apache.org/jira/browse/KAFKA-2429
> Project: Kafka
> Issue Type: Improvement
> Reporter: Ewen Cheslack-Postava
> Assignee: Ewen Cheslack-Postava
>
> We should have some annotations so that we can mark classes as public and
> stable vs. in development and unstable. This will help address two issues.
> First, we already get fairly regular emails on the mailing list about
> non-functioning code because we sometimes check in stubbed out code to get
> started on some new code. Sometimes that also makes it into a release (e.g.
> the stubbed out interface for the new consumer). We don't expect that code to
> work, but it's not obvious to users that it shouldn't. Second, we sometimes
> want to be able to check in imperfect draft code because it's new, expected
> to be unstable, and it helps with reviewing to be able to get something
> smaller checked in and then iterate on it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
