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] [Resolved] (ACCUMULO-2593) Create API annotations with well-defined semantics
Date Wed, 10 Dec 2014 00:03:14 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christopher Tubbs resolved ACCUMULO-2593.
-----------------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 1.7.0)

I'm closing this as "Won't Fix". Guava's @Beta annotation satisfies every goal I had in mind
for this, and in any case, API stability should be subject to project-wide guidelines.

> 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
>
> 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.3.4#6332)

Mime
View raw message