[ovirt-devel] [RFC] reconsidering branching out ovirt-4.2

[Tal Nisan]

It has been decided in the build meeting that we will branch next week on
Monday/Tuesday (VDSM/Engine simultaneously), Sandro's team will take care
of creating the branches and adjusting CI
Eli, is the Engine bump patch for 4.3 in progress?


On Mon, Jan 29, 2018 at 11:23 AM, Martin Perina <mperina at redhat.com> wrote:

>
>
> On Mon, Jan 29, 2018 at 11:14 AM, Sandro Bonazzola <sbonazzo at redhat.com>
> wrote:
>
>>
>>
>> 2018-01-29 11:01 GMT+01:00 Tal Nisan <tnisan at redhat.com>:
>>
>>> For alignment purposes between the projects we should consider branch
>>> ovirt-engine as well.
>>> At this point in time I'm for it, would like to hear any acks/nacks so
>>> we can decide how we proceeed
>>>
>>>
>> Nothing against branching, ack on my side
>>
>
> ​+1 from me
>
> Eli, could you please start preparing patch which will bump master to 4.3
> (db, dc/cluster level ...)?​
>
>
>
>>
>>
>>>
>>> On Mon, Jan 29, 2018 at 9:02 AM, Dan Kenigsberg <danken at redhat.com>
>>> wrote:
>>>
>>>> On Mon, Jan 29, 2018 at 9:39 AM, Francesco Romani <fromani at redhat.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> >
>>>> > It is time again to reconsider branching out the 4.2 stable branch.
>>>> >
>>>> > So far we decided to *not* branch out, and we are taking tags for
>>>> ovirt
>>>> > 4.2 releases from master branch.
>>>> >
>>>> > This means we are merging safe and/or stabilization patches only in
>>>> master.
>>>> >
>>>> >
>>>> > I think it is time to reconsider this decision and branch out for 4.2,
>>>> > because of two reasons:
>>>> >
>>>> > 1. it sends a clearer signal that 4.2 is going in stabilization mode
>>>> >
>>>> > 2. we have requests from virt team, which wants to start working on
>>>> the
>>>> > next cycle features.
>>>> >
>>>> >
>>>> > If we decide to branch out, I'd start the new branch on monday,
>>>> February
>>>> > 5 (1 week from now).
>>>> >
>>>> >
>>>> > The discussion is open, please share your acks/nacks for branching
>>>> out,
>>>> > and for the branching date.
>>>> >
>>>> >
>>>> > I for myself I'm inclined to branch out, so if noone chimes in (!!)
>>>> I'll
>>>> > execute the above plan.
>>>>
>>>> For network we don't see a lot of pending 4.2 work - except for the
>>>> requirement to support el7.5. On the other hand, we too have already a
>>>> patch for 4.3. Thus I'm fine with branching next week.
>>>>
>>>> When you do branch, please make sure to follow Barak Korren's request
>>>> on the
>>>>     [ovirt-devel] [ACTION-REQUIRED] Making accurate CI for oVirt 4.2
>>>> thread.
>>>> _______________________________________________
>>>> Devel mailing list
>>>> Devel at ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>>
>>>
>>>
>>> _______________________________________________
>>> Devel mailing list
>>> Devel at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/devel
>>>
>>
>>
>>
>> --
>>
>> SANDRO BONAZZOLA
>>
>> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
>>
>> Red Hat EMEA <https://www.redhat.com/>
>> <https://red.ht/sig>
>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>>
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>
>
>
> --
> Martin Perina
> Associate Manager, Software Engineering
> Red Hat Czech s.r.o.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20180131/d4c18d35/attachment.html>