hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6775) Update Hadoop Common Sites
Date Thu, 27 May 2010 00:37:38 GMT

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

Chris Douglas commented on HADOOP-6775:

bq. A case I'm worried about is that if we, e.g., rename or remove one of these categories,
then released documentation would no longer make sense. The definition of these terms seems
like a part of the product documentation, not a part of the project policy. How we apply and
enforce the terms is a matter of policy.

As I said, I don't see this as a useful capability. If the project elects to change one of
the labels or its meaning, the page will be required to list that history to be coherent,
e.g. "Versions x.y-x.z used LimitedPrivate instead of StayAwayLusers, but the two may be regarded
as equivalent".

I didn't mean to imply that the mechanics of linking were a sound motivation; I'm pretty sure
that's a solved problem for webpages. I meant that changing these rules need not be tied to
a particular release, but could apply to development in progress. Like 0.21.

bq. Most project policy has typically been documented on the wiki, not the website. Should
we change that?

Sometimes. Do we really need to debate a policy on this?

> Update Hadoop Common Sites 
> ---------------------------
>                 Key: HADOOP-6775
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6775
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Sanjay Radia
>            Assignee: Sanjay Radia
>             Fix For: site
>         Attachments: api_classification.pdf, siteCLassification.patch, siteCLassification2.patch,
> Add documentation on our interface classification scheme to thew common site.

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

View raw message