accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2593) Create API annotations with well-defined semantics
Date Mon, 31 Mar 2014 17:25:18 GMT

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

Christopher Tubbs commented on ACCUMULO-2593:
---------------------------------------------

Oh, I like that. Since we're likely going to have a dependency on guava anyway in the API
module. It's docs seem to define it pretty well, too. If that definition aligns with our requirements,
it seems like a good idea to use it.

> 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)

Mime
View raw message