[
https://issues.apache.org/jira/browse/HADOOP-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665609#action_12665609
]
Doug Cutting commented on HADOOP-5073:
--------------------------------------
> only things that are marked as stable are considered stable, everything else
> is inherently unstable/evolving
That's easier for developers to maintain, but I think more confusing for users,
who might reasonably assume that documented features will be supported going
forward unless marked otherwise. Documentation should be maintainable, but not
at the expense of clear description. So I still prefer marking APIs that are
unstable and leaving stable APIs as the unmarked case. We can use tools like
jdiff to help us audit releases for new features that ought to be marked as
unstable.
> Hadoop 1.0 Interface Classification - scope (visibility - public/private) and
> stability
> ---------------------------------------------------------------------------------------
>
> Key: HADOOP-5073
> URL: https://issues.apache.org/jira/browse/HADOOP-5073
> Project: Hadoop Core
> Issue Type: Sub-task
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
>
> This jira proposes an interface classification for hadoop interfaces.
> The discussion was started in email alias [email protected] in Nov
> 2008.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
