[ https://issues.apache.org/jira/browse/KAFKA-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gwen Shapira updated KAFKA-2429: -------------------------------- Resolution: Fixed Fix Version/s: 0.8.3 Status: Resolved (was: Patch Available) Issue resolved by pull request 133 [https://github.com/apache/kafka/pull/133] > 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 > Fix For: 0.8.3 > > > 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)