I think that both are good. Stable indicates a willingness to maintain
compatibility.
Experimental is a promise that the code will likely be disrupted.
Everything else is likely stable but without guarantees.
On Fri, Oct 7, 2011 at 5:51 PM, Dmitriy Lyubimov (Commented) (JIRA) <
jira@apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/MAHOUT-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123328#comment-13123328]
>
> Dmitriy Lyubimov commented on MAHOUT-831:
> -----------------------------------------
>
> My reasoning is, I am more interested in what is explicitly certified as
> public and stable api, rather than knowing that something is experimental.
>
> > @Experimental annotation to indicate which implementations are not
> intended for production use
> >
> ----------------------------------------------------------------------------------------------
> >
> > Key: MAHOUT-831
> > URL: https://issues.apache.org/jira/browse/MAHOUT-831
> > Project: Mahout
> > Issue Type: Improvement
> > Affects Versions: 0.6
> > Reporter: Sebastian Schelter
> > Assignee: Sebastian Schelter
> > Attachments: MAHOUT-831.patch
> >
> >
>
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators:
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
|