On Fri, Feb 8, 2019 at 9:34 AM Martin Perina <mper...@redhat.com> wrote: > > > > On Thu, Feb 7, 2019 at 10:06 PM Milan Zamazal <mzama...@redhat.com> wrote: >> >> Martin Perina <mper...@redhat.com> writes: >> >> > On Tue, Feb 5, 2019 at 10:37 AM Anton Marchukov <amarc...@redhat.com> >> > 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? > > > I think we need to branch VDSM first and right after branching merge tge > patch introducing 4.4 support https://gerrit.ovirt.org/96632
We want vdsm-4.30.z to support engine-4.4. Thus I don't see why we should wait for anything. https://gerrit.ovirt.org/96632 should be in yesterday. > When VDSM with the patch merged will pass OST, we can branch engine and merge > https://gerrit.ovirt.org/96631 > If we will do that in different order, then master OST will be broken > > But what I wanted to mention is that we should branch either early enough to > be able to deliver 4.3.1 without any issues or right after 4.3.1 is out to > have everything ready before 4.3.2 work starts. > >> >> >> Anton. >> >> >> >> > On 4 Feb 2019, at 15:41, Milan Zamazal <mzama...@redhat.com> wrote: >> >> > >> >> > Anton Marchukov <amarc...@redhat.com> 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 >> >> >> >> >> >> >> >> >> >> >> >> > > > > -- > Martin Perina > Associate Manager, Software Engineering > Red Hat Czech s.r.o. > _______________________________________________ > Devel mailing list -- devel@ovirt.org > To unsubscribe send an email to devel-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/HVBZ4UAZGGSARWLNH2BI377GGXNSO4MV/ _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/2FHSHOODKAA6ILV3K32GHVSWBNJ6E6XG/
