[
https://issues.apache.org/jira/browse/HADOOP-14897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176718#comment-16176718
]
Chris Douglas commented on HADOOP-14897:
----------------------------------------
Thanks [~templedf]. This was filed neutrally, in case there are really
compelling reasons for the requirement.
[[email protected]], you raised this in HADOOP-13714. I agree that
patch versions should, except when addressing security vulnerabilities or other
"must fix" issues, remain stable between patch releases. Given that our major
releases tend to be long-lived, what would be a reasonable policy for native
deps in minor releases? Is there a set of standards used by packagers we could
adopt?
If our compatibility guidelines are setting users' expectations, I hesitate to
promise more than best-effort, here.
> Loosen compatibility guidelines for native dependencies
> -------------------------------------------------------
>
> Key: HADOOP-14897
> URL: https://issues.apache.org/jira/browse/HADOOP-14897
> Project: Hadoop Common
> Issue Type: Bug
> Components: documentation, native
> Reporter: Chris Douglas
> Assignee: Daniel Templeton
> Priority: Blocker
>
> Within a major version, the compatibility guidelines forbid raising the
> minimum required version of any native dependency or tool required to build
> native components.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
