[
https://issues.apache.org/jira/browse/HADOOP-13714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995272#comment-15995272
]
Daniel Templeton commented on HADOOP-13714:
-------------------------------------------
Fair points. Many of the examples you cited are cases where the guidelines
were vague or missing. Call me naïvely optimistic (because I am), but my hope
is that if we can clean up those areas and make the guidelines a first-class
citizen in the development process, we can make a stronger compatibility
promise.
{quote}They don't care.{quote}
I prefer to think that they're not yet properly educated in the importance of
compatibility. In the cases I've seen where something was rushed through
because a vendor needed to keep a promise, the results were often suboptimal.
The first step to reining that kind of behavior in is having and clear and
comprehensive policies. That's the point of this JIRA. The next step is making
the policies front and center in the development process. There isn't a JIRA
for that one yet.
I don't think we're in disagreement.
> 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
> Attachments: HADOOP-13714.WIP-001.patch
>
>
> 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]
