[ovirt-devel] Re: Vdsm: Small version numbering change?

[Milan Zamazal]

Nir Soffer  writes:

> On Thu, Dec 17, 2020 at 1:04 PM Milan Zamazal  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
> ...

I think this is a good idea.  We have already been using 4-part
versioning for stable updates (e.g. v4.40.26.* for 4.4.2 updates) so it
shouldn't cause any trouble.  With the new scheme, we would simply use
4-part versioning all the time, both on master and stable branches.

The suggested versioning change got positive responses and I think Nir's
proposal is a further improvement.  If nobody objects, we can start
using it with the first 4.4.5 build on master.

>> 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/
___
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/CLIC47HEICXCJQDN6B6NKAEIFU2ME6HB/

[ovirt-devel] Re: Vdsm: Small version numbering change?

[Nir Soffer]

On Thu, Dec 17, 2020 at 1:04 PM Milan Zamazal  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 -- 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/
___
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/APVMRCD7CIF7MRRAQF75WTOCQEHQ7JML/

[ovirt-devel] Re: Vdsm: Small version numbering change?

[Ales Musil]

On Thu, Dec 17, 2020 at 12:03 PM Milan Zamazal  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 

amu...@redhat.comIM: amusil

___
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/