On Thu, Dec 17, 2020 at 1:04 PM Milan Zamazal <[email protected]> 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.
Based on older builds 4.40.59 may be an issue, and 4.50.500 is a little too ugly. How about using something similar to engine (currently ovirt-engine-4.4.4.7) v4.40.50.1 v4.40.50.2 ... v4.40.50.12 v4.40.60.1 v4.40.60.2 ... > What do you think? > > Regards, > Milan > _______________________________________________ > Devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected]/message/Q5UK33GMOOAORXFQCBKCPESMNN5Q5RQO/
_______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/APVMRCD7CIF7MRRAQF75WTOCQEHQ7JML/
