On Fri, Aug 10, 2012 at 4:00 PM, Ewan Mellor wrote:
>> -Original Message-
>> From: David Nalley [mailto:da...@gnsa.us]
>> Sent: 10 August 2012 12:56
>> To: cloudstack-dev@incubator.apache.org
>> Cc: Ewan Mellor
>> Subject: Re: [ASFCS40] CloudStack 4.
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: 10 August 2012 12:56
> To: cloudstack-dev@incubator.apache.org
> Cc: Ewan Mellor
> Subject: Re: [ASFCS40] CloudStack 4.0 release plan
>
> >
> > The only exception I would make to th
>
> The only exception I would make to the "everything in 4.0" rule is for
> documentation. I don't see any value in branching the docs, and I want to
> make sure that we can keep updating the docs at a fast pace even as we're
> deliberately slowing down the rate of change on the code. For thi
> -Original Message-
>
> [Snip]
>
> +1, from monday on we'll have a 4.0 branch.
>
> That means however that you have to submit bugs fixes into master and
> 4.0.x, right?
Yes, that's right. All changes should go into master, and anything that we
want for 4.0 should go into the release b
On Aug 10, 2012, at 1:19 AM, Wido den Hollander wrote:
> That means however that you have to submit bugs fixes into master and 4.0.x,
> right?
yes
On 08/10/2012 02:27 AM, Ewan Mellor wrote:
-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com]
[Snip]
Thinking about the milestone along those lines, I agree that cutting a
release branch over the weekend is a good thing. This is specifically
because of the pendin
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
>
> [Snip]
>
> Thinking about the milestone along those lines, I agree that cutting a
> release branch over the weekend is a good thing. This is specifically
> because of the pending review board submissions tha
