You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2014/03/31 19:09:19 UTC

[jira] [Commented] (ACCUMULO-2593) Create API annotations with well-defined semantics

    [ https://issues.apache.org/jira/browse/ACCUMULO-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955391#comment-13955391 ] 

Sean Busbey commented on ACCUMULO-2593:
---------------------------------------

[Guava's Beta annotation|http://docs.guava-libraries.googlecode.com/git-history/v14.0.1/javadoc/com/google/common/annotations/Beta.html] would be one simple way to implement this.

> Create API annotations with well-defined semantics
> --------------------------------------------------
>
>                 Key: ACCUMULO-2593
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2593
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>            Reporter: Christopher Tubbs
>             Fix For: 1.7.0
>
>
> Conveying information about the stability of the API over time can be difficult.
> We should create annotations with well-defined semantics to convey information, like whether a class/method is "experimental" or "stable" or something else, and what those mean. These annotations should be well documented.



--
This message was sent by Atlassian JIRA
(v6.2#6252)