<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 class="">On Mon, May 22, 2017 at 12:52 PM, Yaniv Kaul <<a href="mailto:ykaul@redhat.com">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">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. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Just branching takes a few<br>
seconds, and almost no resources (except for mental ones, in developers'<br>
minds). CI takes more time and more resources.<br>
<span class=""><br>
> so we'll<br>
> learn from the future if we should branch sooner or is it OK to wait - and<br>
> until when.<br>
<br>
</span>We had recently a private discussion about this, with no final conclusion<br>
AFAIR. I suggested (and repeat now) to fully automate this - so that project<br>
maintainers have in the gerrit UI checkboxes for CI per branch. This definitely<br>
takes time, and was considered not worth it, with the assumption that if we do<br>
our work well, we almost never need z branches - that we should aim to push<br>
and merge almost all the patches for some z version right after z-1 was<br>
released, and not postpone this to later on, when we already want to work on<br>
z+1 - and those late-comers that do want/need a branch should verify their<br>
patches manually and not need CI.<br>
<span class="im HOEnZb"><br>
> Y.<br>
><br>
>><br>
>><br>
>><br>
>> Bests,<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>
><br>
><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>
<br>
<br>
<br>
</span><span class="HOEnZb"><font color="#888888">--<br>
Didi<br>
</font></span><div class="HOEnZb"><div class="h5">______________________________<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>
<br>
<br>
</div></div></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>