<div dir="ltr">In order to prevent the confusion of people which occurs in the middle of a work day not knowing whether their patches are included or not, Sandro and I will merge tonight.<div>Team leads - please make sure to let your teams know that starting tomorrow morning all 4.2.2 Engine content should be backported into the stable branch as well</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 2, 2018 at 10:22 AM, Francesco Romani <span dir="ltr"><<a href="mailto:fromani@redhat.com" target="_blank">fromani@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We agreed to branch out on Tuesday, February 6.<br>
<br>
<br>
After that, we will lift any restriction for patches in master branch:<br>
it is up to each team to decide which patches they want to submit, and<br>
which patches they want to backport, following the usual rules.<br>
<br>
<br>
E.g. nothing prevents anyone to submit refactoring or large changes to<br>
master *and* to propose them for backport to stable branch(es) later,<br>
following the usual steps.<br>
<br>
<br>
Bests,<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
On 01/29/2018 08:39 AM, Francesco Romani wrote:<br>
> Hi all,<br>
><br>
><br>
> It is time again to reconsider branching out the 4.2 stable branch.<br>
><br>
> So far we decided to *not* branch out, and we are taking tags for ovirt<br>
> 4.2 releases from master branch.<br>
><br>
> This means we are merging safe and/or stabilization patches only in master.<br>
><br>
><br>
> I think it is time to reconsider this decision and branch out for 4.2,<br>
> because of two reasons:<br>
><br>
> 1. it sends a clearer signal that 4.2 is going in stabilization mode<br>
><br>
> 2. we have requests from virt team, which wants to start working on the<br>
> next cycle features.<br>
><br>
><br>
> If we decide to branch out, I'd start the new branch on monday, February<br>
> 5 (1 week from now).<br>
><br>
><br>
> The discussion is open, please share your acks/nacks for branching out,<br>
> and for the branching date.<br>
><br>
><br>
> I for myself I'm inclined to branch out, so if noone chimes in (!!) I'll<br>
> execute the above plan.<br>
><br>
><br>
<br>
--<br>
Francesco Romani<br>
Senior SW Eng., Virtualization R&D<br>
Red Hat<br>
IRC: fromani github: @fromanirh<br>
<br>
______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br>
</div></div></blockquote></div><br></div>