<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 29, 2018 at 11:01 AM, Tal Nisan <span dir="ltr"><<a href="mailto:tnisan@redhat.com" target="_blank">tnisan@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 dir="ltr">For alignment purposes between the projects we should consider branch ovirt-engine as well.<div>At this point in time I'm for it, would like to hear any acks/nacks so we can decide how we proceeed</div></div></blockquote><div><br></div><div>+1 from me<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div class="h5"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 29, 2018 at 9:02 AM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@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, Jan 29, 2018 at 9:39 AM, Francesco Romani <<a href="mailto:fromani@redhat.com" target="_blank">fromani@redhat.com</a>> wrote:<br>
</span><span>> 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>
</span>For network we don't see a lot of pending 4.2 work - except for the<br>
requirement to support el7.5. On the other hand, we too have already a<br>
patch for 4.3. Thus I'm fine with branching next week.<br>
<br>
When you do branch, please make sure to follow Barak Korren's request on the<br>
[ovirt-devel] [ACTION-REQUIRED] Making accurate CI for oVirt 4.2<br>
thread.<br>
<div class="m_-8811042510459854973HOEnZb"><div class="m_-8811042510459854973h5">______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br>
</div></div></blockquote></div><br></div></div></div></div></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></div></div>