[ovirt-devel] Re: 4.3 Branching

Martin Perina <mperina(a)redhat.com&gt; writes: > On Tue, Feb 5, 2019 at 10:37 AM Anton Marchukov <amarchuk(a)redhat.com&gt; wrote: > >> Hello Milan. >> >> We do not necessary need it earlier, but we want to have some date in >> mind, so we can plan our CI work accordingly. >> >> Any thoughts for engine? Should it also target Feb 18? >> > > On Feb 19th we should release oVirt 4.3.1 RC (4.3.1 GA na Feb 26th along > with RHV 4.3 beta 2), so I'd say let's branch after the final 4.3.1 build > ... I believe we needn't branch out Vdsm and Engine on the same date, right? So we can branch out Vdsm earlier than Engine, around Feb 18-19, is it OK?

>> Anton. >> >> > On 4 Feb 2019, at 15:41, Milan Zamazal <mzamazal(a)redhat.com&gt; wrote: >> > >> > Anton Marchukov <amarchuk(a)redhat.com&gt; writes: >> > >> >> Since oVirt 4.3.0 released are we ready to branch master into 4.3? >> > >> > Regarding Vdsm, there is still an ongoing storage work for 4.3 and no >> > really strong pressure for branching out 4.3 I'm aware of. For that >> > reason, Vdsm developers have agreed that we could create Vdsm ovirt-4.3 >> > branch on February 18 (and no significantly later than that). If the >> > branch is needed earlier for infra or other reasons, we can make it. >> > Storage work would have to be backported, but that can be mostly trivial >> > if an initial master-merge rush is avoided. >> > >> > Thanks, >> > Milan >> >> -- >> Anton Marchukov >> Team Lead - Release Management - RHV DevOps - Red Hat >> >> >> >> >> >>