On Thu, Dec 17, 2020 at 12:03 PM Milan Zamazal <mzama...@redhat.com> wrote:
> Hi, > > we have a nice coincidence now that Vdsm 4.40.40 corresponds to > ovirt-4.4.4 branch. Would we like to use this opportunity to make Vdsm > versions aligned with oVirt 4.4.* versions? > > We can tag the next master build, which will be no longer part of > ovirt-4.4.4 branch, as v4.40.50. Or we could tag it as v4.40.500 to be > on the safe side, but both 4.4.3 and 4.4.4 had less than 10 tags on > master, so it's probably not needed and there is always v4.40.591-like > workaround available. > > What do you think? > > Regards, > Milan > _______________________________________________ > Devel mailing list -- devel@ovirt.org > To unsubscribe send an email to devel-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/Q5UK33GMOOAORXFQCBKCPESMNN5Q5RQO/ > Hi, +1 it is easier to connect the oVirt version and vdsm version this way. Thanks, Ales -- Ales Musil Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amu...@redhat.com IM: amusil <https://red.ht/sig>
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/RGKXLAJVQ7VDCS4ZP4GQHUBPRNLCI6LH/
