> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Friday, March 14, 2014 7:43 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Differences between 4.3 and 4.3-forward
>
> Yes, and we definitely cannot just take all of 4.3.1
le 4.3 is
> going through RC. It is meant for maintenance release.
>
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Friday, March 14, 2014 7:36 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Differences between 4.3 and 4.3-f
riday, March 14, 2014 1:38 AM
> To: dev@cloudstack.apache.org
> Subject: RE: Differences between 4.3 and 4.3-forward
>
> Will these automatically go into 4.3.1, do we know if they've gone
> into master as well?
>
> Otherwise does this mean we have a load of bug fixes which
@cloudstack.apache.org
> Subject: RE: Differences between 4.3 and 4.3-forward
>
> Will these automatically go into 4.3.1, do we know if they've gone into
> master as well?
>
> Otherwise does this mean we have a load of bug fixes which we're not
> putting into 4.3.0 whic
: Differences between 4.3 and 4.3-forward
Will these automatically go into 4.3.1, do we know if they've gone into master
as well?
Otherwise does this mean we have a load of bug fixes which we're not putting
into 4.3.0 which could potentially become orphaned in the 4.3-forward branch?
(this qu
Paul, they might be disapproved patches as well.
On Fri, Mar 14, 2014 at 9:38 AM, Paul Angus wrote:
> Will these automatically go into 4.3.1, do we know if they've gone into
> master as well?
>
> Otherwise does this mean we have a load of bug fixes which we're not putting
> into 4.3.0 which cou
Will these automatically go into 4.3.1, do we know if they've gone into master
as well?
Otherwise does this mean we have a load of bug fixes which we're not putting
into 4.3.0 which could potentially become orphaned in the 4.3-forward branch?
(this query may be just my ignorance regarding ACS b
