[
https://issues.apache.org/jira/browse/HADOOP-14964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267686#comment-16267686
]
Chris Douglas commented on HADOOP-14964:
----------------------------------------
bq. The patch for 2.8.3 will be cherry picked from branch-2
Please cherry-pick from branch-2.9 to branch-2.8, then from branch-2.8 to
branch-2.8.3 so the lineage is clear.
The concerns from the release thread:
# *Dependencies* Since the OSS artifact is not shaded, does it introduce
dependencies that could conflict with versions used by clients?
# *Upgrade* 2.9.0 does not contain Aliyun OSS. If we release 2.8.3, users
cannot upgrade to 2.9.x without regressing on this feature.
# *Timing* 2.8.3 contains critical bug fixes, so this needs to wrap up quickly
if it will be included.
# *Release policy* This should not contradict Hadoop's [compatibility
guidelines|https://hadoop.apache.org/docs/r3.0.0-beta1/hadoop-project-dist/hadoop-common/Compatibility.html].
1-3 are concerns that have a technical remediation:
For (1), what are all the transitive dependencies for this module? If the SDK
uses dependencies that already ship with 2.8.2, then we may not need shading,
but any new, visible dependency needs to be added to the release notes and
classify this as an incompatible change. If the number of new, visible
dependencies is zero (by shading or reuse), then (1) is trivially satisfied.
For (2), if we take the current branch-2.9 and cut a 2.9.1 release, that would
tranquilize anxiety about the upgrade path. [~Sammi], would you be able to RM
this? [~asuresh] and [~subru] may be able to help by providing pointers to
release docs.
(3) Is not a problem, as there are some blocker issues and the patch is
available.
As policy, (4) is stickier. Even releasing this with 2.9.1 doesn't strictly
adhere to our rules, but it's better than adding another, active release
branch. The case for 2.8.3 is more problematic. The cadence for 2.8.x will
decelerate more rapidly than 2.9.x, so fixes to Aliyun OSS will be released
less often. We may not do its users a favor by including an outdated client
with their 2.8 clusters. Frankly, maintenance is also simpler when we disallow
feature backports into patch releases, rather than discussing the merits of
each one. This can't become a precedent; it takes too much time.
Personally, if 1-3 are addressed and folks working on the module still want to
go ahead with it, then I'd support a 2.8.3 release with Aliyun OSS.
> AliyunOSS: backport Aliyun OSS module to branch-2
> -------------------------------------------------
>
> Key: HADOOP-14964
> URL: https://issues.apache.org/jira/browse/HADOOP-14964
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/oss
> Reporter: Genmao Yu
> Assignee: SammiChen
> Fix For: 2.9.1
>
> Attachments: HADOOP-14964-branch-2.000.patch,
> HADOOP-14964-branch-2.8.000.patch, HADOOP-14964-branch-2.8.001.patch,
> HADOOP-14964-branch-2.9.001.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
