hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Radia (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6668) Apply audience and stability annotations to classes in common
Date Fri, 30 Apr 2010 17:44:54 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862763#action_12862763

Sanjay Radia commented on HADOOP-6668:

Tom, based on my first glance at the list of criteria that you state above and the patch you
have attached it appears that you have also ignored the original jira Hadoop-5073 and the
very concrete proposal in that Jira:
HADOOP-6289,  which was linked to Hadoop-5073,  used that concrete proposal as the starting
(BTW HADOOP-6668 should have been linked to 5073 - if it had been,  the duplication might
have been detected.)

I suggest that we first come to an agreement on the criteria. 
I will shortly post a my feedback on the criteria you have state above and contrast this against
those used on the proposal in Hadoop-6289.

> Apply audience and stability annotations to classes in common
> -------------------------------------------------------------
>                 Key: HADOOP-6668
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6668
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: documentation
>            Reporter: Tom White
>            Assignee: Tom White
>            Priority: Blocker
>             Fix For: 0.21.0
>         Attachments: HADOOP-6668.patch, HADOOP-6668.patch, HADOOP-6668.patch, HADOOP-6668.patch,
> Mark private implementation classes with the InterfaceAudience.Private or InterfaceAudience.LimitedPrivate
annotation to exclude them from user Javadoc and JDiff.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message