OK, thanks, David.

We can create a new branch for this Review Request and merge it to master
once 4.5 is cut.

On Mon, Oct 6, 2014 at 12:09 PM, David Nalley <[email protected]> wrote:

> On Mon, Oct 6, 2014 at 12:49 PM, Mike Tutkowski
> <[email protected]> wrote:
> > Hi David,
> >
> > So, I know we're a ways past code freeze, but we seem to have been
> (rightly)
> > focusing more of our dev effort as a community on 4.3.1 and 4.4.1 lately.
> >
>
> Yes, as I've stated elsewhere, I am in some ways waiting for 4.4.1. to
> close before we try and process a 4.5.0 release.
>
> > It seems that check-ins have gone into master in the recent past and that
> > you felt they should not be reverted.
>
> I actually think several of these should be reverted. In particular,
> some of the current 4.5 blockers would not exist if not for those.
> I am contemplating whether the right way forward is to continue with
> master as the release branch or whether I should branch 4.5 before the
> problematic features landed and cherry pick over bug fixes as
> appropriate.
>
> >
> > That being the case, Marcus and I have completed a review of the
> following
> > and were wondering if it would be OK to put it in master?
> >
> > https://reviews.apache.org/r/25772/
> >
> > Thanks!
> >
>
> I'd prefer not to, regardless, I wouldn't expect it to be in 4.5.0
>
> --David
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: [email protected]
o: 303.746.7302
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>*™*

Reply via email to