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 AA302200B2D for ; Thu, 16 Jun 2016 08:29:34 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A7401160A52; Thu, 16 Jun 2016 06:29:34 +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 F1219160A51 for ; Thu, 16 Jun 2016 08:29:33 +0200 (CEST) Received: (qmail 85130 invoked by uid 500); 16 Jun 2016 06:29:28 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 85119 invoked by uid 99); 16 Jun 2016 06:29:27 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jun 2016 06:29:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 5723E180542 for ; Thu, 16 Jun 2016 06:29:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -6.427 X-Spam-Level: X-Spam-Status: No, score=-6.427 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id VXssbmHyJqm5 for ; Thu, 16 Jun 2016 06:29:25 +0000 (UTC) Received: from mx141.netapp.com (mx141.netapp.com [216.240.21.12]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 2EE925F3A1 for ; Thu, 16 Jun 2016 06:29:23 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.26,478,1459839600"; d="scan'208";a="125297213" Received: from hioexcmbx02-prd.hq.netapp.com ([10.122.105.35]) by mx141-out.netapp.com with ESMTP; 15 Jun 2016 23:29:15 -0700 Received: from HIOEXCMBX05-PRD.hq.netapp.com (10.122.105.38) by hioexcmbx02-prd.hq.netapp.com (10.122.105.35) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Wed, 15 Jun 2016 23:29:14 -0700 Received: from HIOEXCMBX05-PRD.hq.netapp.com ([::1]) by hioexcmbx05-prd.hq.netapp.com ([fe80::ec82:8bad:2d2f:5605%21]) with mapi id 15.00.1156.000; Wed, 15 Jun 2016 23:29:14 -0700 From: "Tutkowski, Mike" To: "dev@cloudstack.apache.org" Subject: Re: Release-Management Question about New API Plug-in Thread-Topic: Release-Management Question about New API Plug-in Thread-Index: AQHRx2/9CdgfKiM/ak+qPu5YJdpa+5/sFOSA//+NCEo= Date: Thu, 16 Jun 2016 06:29:13 +0000 Message-ID: <2BD79935-75B3-41E4-BC1C-60071FE215ED@netapp.com> References: <1466041324496.26183@netapp.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 archived-at: Thu, 16 Jun 2016 06:29:34 -0000 OK - I can always deliver the plug-in for 4.6 directly to my customers and = first check it into the CloudStack repo maybe in 4.10 or later. > On Jun 16, 2016, at 12:21 AM, Rajani Karuturi wrote: >=20 > "We will only fix bugs in this release branch, no back porting of new > features" - > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+principles= +for+Apache+CloudStack+4.6+and+up >=20 > I would prefer a PR on master for 4.9+ >=20 >=20 >=20 > ~Rajani >=20 > On Thu, Jun 16, 2016 at 7:12 AM, Tutkowski, Mike > wrote: >=20 >> Hi, >>=20 >>=20 >> This is mainly a release-management question, but - of course - anyone w= ho >> knows, please feel free to comment. >>=20 >>=20 >> I have been developing a new API plug-in for a customer. The customer is >> using CloudStack 4.6. >>=20 >>=20 >> I'd like to contribute the plug-in to our official repo, but I'm wonderi= ng >> if I can open a PR as far back as 4.6 (and, of course, I'd like to have >> this plug-in in all subsequent releases, as well). >>=20 >>=20 >> Thoughts on this? >>=20 >>=20 >> Thanks! >>=20 >> Mike >>=20