Re: Release-Management Question about New API Plug-in

[Will Stevens]

That is assuming the RM is willing to do that and forward merge it up to
the latest master.

Technically for 4.9, we supported merging into 4.7 and 4.8 and master.
Once 4.9 is release, the officially supported branches will be 4.8, 4.9 and
master.  Rajani is correct that ideally new features will go into master
and only bug fixes will be added to the older branches, but with an
increased release pace, this may add unintended work on PR authors if their
features don't get into the upcoming release.

Hope that helps...

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Thu, Jun 16, 2016 at 10:46 PM, John Burwell 
wrote:

> Mike,
>
> Anyone can submit a PR against any branch.  If they can get 2 LGTMs for
> it, it will be merged.  After that, you could create a new 4.6 RC, and open
> a vote for it.  While there is nothing procedurally that prevents someone
> from following this process, it is unlikely that the release vote would
> muster interest to pass.
>
> Thanks,
> -John
>
> >
> john.burw...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London VA WC2N 4HSUK
> @shapeblue
>
>
> On Jun 16, 2016, at 2:29 AM, Tutkowski, Mike 
> wrote:
> >
> > 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:
> >>
> >> "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.tutkow...@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
> >>>
>
>

Re: Release-Management Question about New API Plug-in

[Tutkowski, Mike]

Sounds good, John

I think it will be easier if I just release it directly to the customer.

I can always port it to the latest CloudStack version later, if I'd like to.

> On Jun 16, 2016, at 8:46 PM, John Burwell  wrote:
> 
> Mike,
> 
> Anyone can submit a PR against any branch.  If they can get 2 LGTMs for it, 
> it will be merged.  After that, you could create a new 4.6 RC, and open a 
> vote for it.  While there is nothing procedurally that prevents someone from 
> following this process, it is unlikely that the release vote would muster 
> interest to pass.
> 
> Thanks,
> -John
> 
> john.burw...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London VA WC2N 4HSUK
> @shapeblue
> 
> 
>> On Jun 16, 2016, at 2:29 AM, Tutkowski, Mike  
>> wrote:
>> 
>> 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:
>>> 
>>> "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 
>>> 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
> 

Re: Release-Management Question about New API Plug-in

[John Burwell]

Mike,

Anyone can submit a PR against any branch.  If they can get 2 LGTMs for it, it 
will be merged.  After that, you could create a new 4.6 RC, and open a vote for 
it.  While there is nothing procedurally that prevents someone from following 
this process, it is unlikely that the release vote would muster interest to 
pass.

Thanks,
-John

> 
john.burw...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London VA WC2N 4HSUK
@shapeblue


On Jun 16, 2016, at 2:29 AM, Tutkowski, Mike  wrote:
> 
> 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:
>> 
>> "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 
>> 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
>>> 

Re: Release-Management Question about New API Plug-in

[Tutkowski, Mike]

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:
> 
> "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 
> 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
>> 

Re: Release-Management Question about New API Plug-in

[Rajani Karuturi]

"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 
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
>

Re: Release-Management Question about New API Plug-in

[Daan Hoogland]

just do it. And as a committer make it on a branch in the apache repo, I'd
say. As a escrow to your customer ;)

On Thu, Jun 16, 2016 at 3:42 AM, Tutkowski, Mike 
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
>



-- 
Daan

Release-Management Question about New API Plug-in

[Tutkowski, Mike]

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