<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 23, 2017 at 11:27 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">
<div text="#000000" bgcolor="#FFFFFF"><span class="">
On 05/22/2017 12:32 PM, Eyal Edri wrote:<br>
<blockquote type="cite">
<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">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>On Mon, May 22, 2017 at 12:52 PM, Yaniv Kaul
<<a href="mailto:ykaul@redhat.com" target="_blank">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" target="_blank">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></span>
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.</div></blockquote><div><br></div><div>+1.</div><div><br></div><div>Also, one thing we can consider for next time is to allow merging earlier on stable branch and if we see that </div><div>we still need patches for 4.1.2, we can always create a new branch from the latest tag for 4.1.2.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><span class=""><br>
<br>
Bests,<br>
<pre class="m_-3555609687216590717moz-signature" cols="72">--
Francesco Romani
Senior SW Eng., Virtualization R&D
Red Hat
IRC: fromani github: @fromanirh</pre>
</span></div>
<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></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><p style="font-family:overpass,sans-serif;margin:0px;padding:0px;font-size:14px;text-transform:uppercase;font-weight:bold"><font color="#cc0000">Eyal edri</font></p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:uppercase"><br></p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;margin:0px 0px 4px;text-transform:uppercase">ASSOCIATE MANAGER</p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;margin:0px 0px 4px;text-transform:uppercase">RHV DevOps</p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;margin:0px 0px 4px;text-transform:uppercase">EMEA VIRTUALIZATION R&D</p><p style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><br></p><p style="font-family:overpass,sans-serif;margin:0px;font-size:10px;color:rgb(153,153,153)"><a href="https://www.redhat.com/" style="color:rgb(0,136,206);margin:0px" target="_blank">Red Hat EMEA</a></p><table border="0" style="color:rgb(0,0,0);font-family:overpass,sans-serif;font-size:medium"><tbody><tr><td width="100px"><a href="https://red.ht/sig" style="color:rgb(17,85,204)" target="_blank"><img src="https://www.redhat.com/profiles/rh/themes/redhatdotcom/img/logo-red-hat-black.png" width="90" height="auto"></a></td><td style="font-size:10px"><a href="https://redhat.com/trusted" style="color:rgb(204,0,0);font-weight:bold" target="_blank">TRIED. TESTED. TRUSTED.</a></td></tr></tbody></table></div><div>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div></div></div></div></div>
</div></div>