cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus <>
Subject Re: marvin master changes in 4.4-forward
Date Tue, 27 May 2014 21:16:20 GMT
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 <>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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message