[ovirt-devel] [vdsm] branching out 4.1.2

Eyal Edri eedri at redhat.com
Tue May 23 08:33:35 UTC 2017


On Tue, May 23, 2017 at 11:27 AM, Francesco Romani <fromani at redhat.com>
wrote:

> On 05/22/2017 12:32 PM, Eyal Edri wrote:
>
>
>
> On Mon, May 22, 2017 at 1:11 PM, Yedidyah Bar David <didi at redhat.com>
> wrote:
>
>> On Mon, May 22, 2017 at 12:52 PM, Yaniv Kaul <ykaul at redhat.com> wrote:
>> >
>> >
>> > On Mon, May 22, 2017 at 11:23 AM, Francesco Romani <fromani at redhat.com>
>> > wrote:
>> >>
>> >> Hi all,
>> >>
>> >>
>> >> patches against the 4.1 branch are piling up, so I'm thinking about
>> >> branching out 4.1.2 tomorrow (20170523)
>> >>
>> >> The activity on the 4.1.2 front was quite low lately, so we should
>> >> expect quite few double backports.
>> >>
>> >>
>> >> Thoughts? I'll go forward and branch if noone objects.
>> >
>> >
>> > 1. Go for it.
>> > 2. Let's see what the outcome is. How many 'merge races' we have, how
>> many
>> > regressions (hopefully none), how much work is poured into it,
>>
>> Do you want for the new branch full CI coverage?
>
>
> 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
> before backporting to the new branch.
>
> Yes, there might be rare occasions where a patch will fail on version
> branch and not stable branch,
> I'm not sure its worth the effort of duplicating all CI resources per
> branch just for it.
> We already don't cover all flows in CI because there are limited
> resources, so I don't see a huge difference here.
>
> We can always run verification on the final bits via manual job before
> releasing to catch such cases.
>
>
> I agree with Eyal. Furthermore 4.1.2 is released, so I expect low-to-none
> activity on that ovirt-4.1.2 branch.
> The merging activity on the branch ovirt-4.1 resumed, the merge window is
> now open again for 4.1.3.
>

+1.

Also, one thing we can consider for next time is to allow merging earlier
on stable branch and if we see that
we still need patches for 4.1.2, we can always create a new branch from the
latest tag for 4.1.2.


>
>
> Bests,
>
> --
> Francesco Romani
> Senior SW Eng., Virtualization R&D
> Red Hat
> IRC: fromani github: @fromanirh
>
>
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>



-- 

Eyal edri


ASSOCIATE MANAGER

RHV DevOps

EMEA VIRTUALIZATION R&D


Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20170523/97c30f1d/attachment.html>


More information about the Devel mailing list