[
https://issues.apache.org/jira/browse/HADOOP-9517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671846#comment-13671846
]
Karthik Kambatla commented on HADOOP-9517:
------------------------------------------
It might make sense to make certain (non-internal) proto files public, and
leave the internal (RM-NM) protos private.
Also, I think the policy on changes to proto files should be:
# Optional fields can be added any time
# Fields can be renamed any time
# Required fields can't be added within a major release
# Field order and type can't be modified within a major release
> Document Hadoop Compatibility
> -----------------------------
>
> Key: HADOOP-9517
> URL: https://issues.apache.org/jira/browse/HADOOP-9517
> Project: Hadoop Common
> Issue Type: Bug
> Components: documentation
> Reporter: Arun C Murthy
> Assignee: Karthik Kambatla
> Attachments: hadoop-9517.patch, hadoop-9517.patch, hadoop-9517.patch,
> hadoop-9517.patch, hadoop-9517-proposal-v1.patch,
> hadoop-9517-proposal-v1.patch
>
>
> As we get ready to call hadoop-2 stable we need to better define 'Hadoop
> Compatibility'.
> http://wiki.apache.org/hadoop/Compatibility is a start, let's document
> requirements clearly and completely.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
