Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
MIME-Version: 1.0
In-Reply-To: <1466041324496.26183@netapp.com>
References: <1466041324496.26183@netapp.com>
From: Rajani Karuturi <rajani@apache.org>
Date: Thu, 16 Jun 2016 11:50:43 +0530
Message-ID: <CAPpf5a0hj_6Prnh-UjgA7Oj6kOMkOW6fBqpca_jq9cK7VQ_6hg@mail.gmail.com>
Subject: Re: Release-Management Question about New API Plug-in
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=001a1135bf38148fad05355f3e45
archived-at: Thu, 16 Jun 2016 06:21:06 -0000

--001a1135bf38148fad05355f3e45
Content-Type: text/plain; charset=UTF-8

"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

I would prefer a PR on master for 4.9+


~Rajani

On Thu, Jun 16, 2016 at 7:12 AM, Tutkowski, Mike <Mike.Tutkowski@netapp.com>
wrote:

> Hi,
>
>
> This is mainly a release-management question, but - of course - anyone who
> knows, please feel free to comment.
>
>
> I have been developing a new API plug-in for a customer. The customer is
> using CloudStack 4.6.
>
>
> I'd like to contribute the plug-in to our official repo, but I'm wondering
> 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).
>
>
> Thoughts on this?
>
>
> Thanks!
>
> Mike
>

--001a1135bf38148fad05355f3e45--