[
https://issues.apache.org/jira/browse/HADOOP-13714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975695#comment-15975695
]
Daniel Templeton commented on HADOOP-13714:
-------------------------------------------
I've been reading up on the history of these guidelines and talking with
[~kasha]. Here's a rough idea of the changes I think we should make:
* Explicitly call out in InterfaceClassification.md when *compatible* changes
are allowed
* Add an explicit definition of what constitutes a compatible change versus an
incompatible change
* Add audience and stability statements for all categories, e.g. all CLI tools
are considered public stable
* Tighten up language to be comprehensive and crystal clear
* Be really clear about what we consider to be the domain of users/admins,
application/plugin/extension developers, and project developers and how we
expect our interfaces to be used
These are things we may want to additionally address:
* Support for security mechanisms/protocols, e.g. SSLv3
* Port assignments
* Log output--it's an interface!
* Log4j settings
* UI plugins
* JHS/ATS data
It would be *really* nice to support this effort by beefing up the JavaDocs
such that they can serve the role of specifying semantic behavior. That's
obviously out of scope for 3.0.0 given the size of the effort, but it's really
hard to talk about semantic compatibility when users are reading source code to
determine behavior.
I'll start work on drafting a patch, and I'll post it for review as soon as
it's ready.
> Tighten up our compatibility guidelines for Hadoop 3
> ----------------------------------------------------
>
> Key: HADOOP-13714
> URL: https://issues.apache.org/jira/browse/HADOOP-13714
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 2.7.3
> Reporter: Karthik Kambatla
> Assignee: Daniel Templeton
> Priority: Blocker
>
> Our current compatibility guidelines are incomplete and loose. For many
> categories, we do not have a policy. It would be nice to actually define
> those policies so our users know what to expect and the developers know what
> releases to target their changes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
