[
https://issues.apache.org/jira/browse/HADOOP-13714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977735#comment-15977735
]
Allen Wittenauer edited comment on HADOOP-13714 at 4/20/17 10:43 PM:
---------------------------------------------------------------------
First: HADOOP-11696 (and those are old stats!)
Second: HADOOP-14333 (most recent, but there are other examples... I'm thinking
of Tez calling to YARN's private universe in particular)
Third: The countless "let's add some edge case feature that 90% of the universe
won't use to fsck's default output" issues
I'm becoming more and more of the opinion that the compatibility guidelines are
useless. People who should know better regularly ignore them. People who are
supposed to help enforce them regularly look the other way if it benefits them
or their company. Core developers read the JavaDocs while the end users read
everything else. There is a huge disconnect in our communication.
To which I say: get rid of major releases. Instead, what would be minor
releases now become majors, and micros become minors. Minors are only for
security holes. (No really. Documentation updates are not allowed.) This
effectively eliminates the need for the vast majority of the compatibility
guidelines and would likely allow Hadoop to claim Semantic Versioning.
(Oh, and on HDFS audit logs? Guess what? Those changed incompatibility at
least three times in 2.x. So yeah, I have zero faith in that document that is
supposed to protect end users.)
was (Author: aw):
First: HADOOP-11696 (and those are old stats!)
Second: HADOOP-14333 (most recent, but there are other examples... I'm thinking
of Tez calling to YARN's private universe in particular)
Third: The countless "let's add some edge case feature that 90% of the universe
won't use to fsck's default output" issues
I'm becoming more and more of the opinion that the compatibility guidelines are
useless. People who should know better regularly ignore them. People who are
supposed to help enforce them regularly look the other way if it benefits them
or their company. Core developers read the JavaDocs while the end users read
everything else. There is a huge disconnect in our communication.
To which I say: get rid of major releases. Instead, what would be minor
releases now become majors, and micros become minors. Minors are only for
security holes. (No really. Documentation updates are not allowed.) This
effectively eliminates the need for the vast majority of the compatibility
guidelines and would likely allow Hadoop to claim Semantic Versioning.
> 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]
