Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A6DFA200D53 for ; Tue, 21 Nov 2017 03:22:07 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A567D160C0D; Tue, 21 Nov 2017 02:22:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id EB57B160BF9 for ; Tue, 21 Nov 2017 03:22:06 +0100 (CET) Received: (qmail 34592 invoked by uid 500); 21 Nov 2017 02:22:06 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 34581 invoked by uid 99); 21 Nov 2017 02:22:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Nov 2017 02:22:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 0DD1F1A1715 for ; Tue, 21 Nov 2017 02:22:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id YA2jklXc-4fm for ; Tue, 21 Nov 2017 02:22:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 6C78F5F523 for ; Tue, 21 Nov 2017 02:22:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E74BAE041F for ; Tue, 21 Nov 2017 02:22:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id DBB3023F05 for ; Tue, 21 Nov 2017 02:22:00 +0000 (UTC) Date: Tue, 21 Nov 2017 02:22:00 +0000 (UTC) From: "Kai Zheng (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-14964) AliyunOSS: backport Aliyun OSS module to branch-2 and 2.7+ branches MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 21 Nov 2017 02:22:07 -0000 [ https://issues.apache.org/jira/browse/HADOOP-14964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260174#comment-16260174 ] Kai Zheng commented on HADOOP-14964: ------------------------------------ Thanks Chris for the comments! bq. In the future, please raise active backports in the release threads. Yes, it's a miss we didn't raise this in a release thread instead of here. I admit we didn't plan this well beforehand then found our users want this feature in 2.7+ releases instead of waiting for the 3.0 release. The module was worked out actually in the last year and we didn't make it in a release since then. A real bad and I'm sorry for that :(. bq. It would have been simpler if this issue had been visible before 2.9.0 was released. Now that 2.9.0 is out, this should target 2.10... Oops, I probably got what you meant. So 2.9.0 would be the right chance for a major feature to be in, and after that, 2.9.1+ will just be patch releases for bug fixes, right? bq. As discussed on the dev list, we have not released other FS plugins with patch releases. While initially awkward, it prevents situations where we need to generate a release in a moribund branch for an active component. Ok, I saw the problem. I don't want to cause mess as you said if it's the community release convention. I also received some similar concern from Steve. I'll try to align with my side and see how to proceed. As you suggested, looks like 2.9.1 would be good to target and for 2.7/2.8 releases we provide separate patches or jars hosted somewhere. > AliyunOSS: backport Aliyun OSS module to branch-2 and 2.7+ branches > ------------------------------------------------------------------- > > 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 > Attachments: HADOOP-14964-branch-2.000.patch, HADOOP-14964-branch-2.8.000.patch, HADOOP-14964-branch-2.8.001.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org