Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of shadowsor@gmail.com designates
 209.85.128.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGQtxvYqHaTKztJk+Y1r-PH470HLcMGsYDcT7pzCmcmj1+6YKA@mail.gmail.com>
References: 
 <CALFpzo7UNv3pLT_=XUf4WNMoFUMGgg_YsOxdWsb8eLkGyyiwwg@mail.gmail.com>
	<CAGQtxvYqHaTKztJk+Y1r-PH470HLcMGsYDcT7pzCmcmj1+6YKA@mail.gmail.com>
Date: Tue, 27 May 2014 15:16:20 -0600
Message-ID: 
 <CALFpzo5ezvABPGNtAt66vhyTP6GPdiqVYEK2bb6vCiwTi3o_6A@mail.gmail.com>
Subject: Re: marvin master changes in 4.4-forward
From: Marcus <shadowsor@gmail.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=bcaec51b1daf074b5a04fa683543

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

My impression was that we should change as little as possible once a
release is cut. We fix bugs, but we don't change code just to make it more
maintainable, for fear of introducing more bugs or regressing the known
state of the release.

That aside, this fix is fairly minor so I'll probably just drop it. The
only question that remains is what people should do going forward when a
change needs to be made to an RC branch that is incompatible with its
"-forward" branch.


On Tue, May 27, 2014 at 2:23 PM, Daan Hoogland <daan.hoogland@gmail.com>wrote:

> Marcus,
>
> I don't see why only fixes should go in 4.4. It should have been
> announced before feature freeze but there might be good reasons to
> refactor if it improves maintainability or removes bugs. You can
> revert the related commit and apply yours. or mix them.
>
> regards
>

--bcaec51b1daf074b5a04fa683543--