<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 05/22/2017 12:32 PM, Eyal Edri wrote:<br>
<blockquote type="cite"
cite="mid:CACuV_Hq6yg6qjDuhhf+5xnO7HL5jFxHKM_4ouYpK0RAuzpNw_g@mail.gmail.com">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, May 22, 2017 at 1:11 PM,
Yedidyah Bar David <span dir="ltr"><<a
href="mailto:didi@redhat.com" target="_blank"
moz-do-not-send="true">didi@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On Mon, May 22, 2017 at 12:52 PM, Yaniv Kaul
<<a href="mailto:ykaul@redhat.com"
moz-do-not-send="true">ykaul@redhat.com</a>> wrote:<br>
><br>
><br>
> On Mon, May 22, 2017 at 11:23 AM, Francesco Romani
<<a href="mailto:fromani@redhat.com"
moz-do-not-send="true">fromani@redhat.com</a>><br>
> wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>><br>
>> patches against the 4.1 branch are piling up,
so I'm thinking about<br>
>> branching out 4.1.2 tomorrow (20170523)<br>
>><br>
>> The activity on the 4.1.2 front was quite low
lately, so we should<br>
>> expect quite few double backports.<br>
>><br>
>><br>
>> Thoughts? I'll go forward and branch if noone
objects.<br>
><br>
><br>
> 1. Go for it.<br>
> 2. Let's see what the outcome is. How many 'merge
races' we have, how many<br>
> regressions (hopefully none), how much work is
poured into it,<br>
<br>
</span>Do you want for the new branch full CI coverage? </blockquote>
<div><br>
</div>
<div>I don't think it should, since the stable branch which
is a superset of it should all the patches as well and
will fail</div>
<div>before backporting to the new branch.</div>
<div><br>
</div>
<div>Yes, there might be rare occasions where a patch will
fail on version branch and not stable branch,</div>
<div>I'm not sure its worth the effort of duplicating all CI
resources per branch just for it.</div>
<div>We already don't cover all flows in CI because there
are limited resources, so I don't see a huge difference
here.</div>
<div><br>
</div>
<div>We can always run verification on the final bits via
manual job before releasing to catch such cases. <br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
I agree with Eyal. Furthermore 4.1.2 is released, so I expect
low-to-none activity on that ovirt-4.1.2 branch.<br>
The merging activity on the branch ovirt-4.1 resumed, the merge
window is now open again for 4.1.3.<br>
<br>
Bests,<br>
<pre class="moz-signature" cols="72">--
Francesco Romani
Senior SW Eng., Virtualization R&D
Red Hat
IRC: fromani github: @fromanirh</pre>
</body>
</html>