<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">+1<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 1, 2016 at 12:51 PM, Nir Soffer <span dir="ltr"><<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
We are going to branch 4.0 today, and it is a good time to update our<br>
versioning scheme.<br>
<br>
I suggest to use the standard ovirt versioning, use by most projects:<br>
<br>
1. master<br>
<br>
vdsm-4.19.0-201606011345.gitxxxyyy<br>
<br>
2. 4.0<br>
<br>
vdsm-4.18.1<br>
<br>
The important invariant is that any build from master is considered newer<br>
compare with the stable builds, since master always contain all stable<br>
code, and new code.<br>
<br>
Second invariant, the most recent build from master is always newer compared<br>
with any other master build - the timestamp enforces this.<br>
<br>
Thoughts?<br>
<br>
Nir<br>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><br>
</blockquote></div><br></div></div>