<div dir="ltr">Again, I should understand the direction you ack here ... and its not clear in any way I try to read it<div>lets summaries current status:<br><div>master == v4.17.999 (I recalled 4.18 tag for 4.0... probably it hasn't happened yet)</div></div><div>ovit-3.6.3 last commit points to v4.17.23 (and also contains in its history 4.17.22 4.17.21 4.17.20 and 4.17.19</div><div>ovirt-3.6 == was not tagged since v4.17.19<br></div><div><br></div><div>So, as far as I see - last "official published" version is tagged anyway. once we'll finish with z-streams, we can continue tagging only on ovirt-3.6 branch. but as long as we publish new snapshots (or z-stream releases as I call them) we can continue the tagging only on ovirt-3.6.3 branch </div><div><br></div><div>The rest of your suggestions can't help in any way. if you prefer you can use 4th level versioning (4.17.x-y) later on. but currently we just continue to raise the current 4.17 we have</div><div> </div><div>now, getting back to the origin mail that Sandro sent:</div><div><br></div><div>""" snip</div><div><div style="font-size:12.8px">> <a href="http://jenkins.ovirt.org/job/vdsm_3.6_build-artifacts-el7-x86_64/178/artifact/exported-artifacts/vdsm-4.17.19-32.git171584b.el7.centos.src.rpm" target="_blank" style="color:rgb(92,53,102);font-family:Helvetica,Arial,sans-serif;font-size:13px">vdsm-4.17.19-32.git171584b.el7.centos.src.rpm</a> because the last tag on the 3.6 branch was 4.17.19 and new tags have been created in different branches.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">this is correct - no problem with that approach, new tag still will be higher then 4.17.19 as we see with 4.17.23</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">> This make impossible to upgrade from stable (4.17.23) to latest snapshot.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">But we just said that stable (ovirt-3.6) is 4.17.19 and latest is 4.17.23 - so it sounds right to me.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">> This also break dependencies on other projects requiring the latest released version like hosted engine.</div></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">No its not. HE may require 4.17.23 which is the latest we publish as part of 3.6.3</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">"""</div><div><br></div><div>Yaniv Bronhaim.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 7, 2016 at 1:58 PM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Mon, Mar 07, 2016 at 12:06:32PM +0200, Nir Soffer wrote:<br>
> +1<br>
><br>
> On Mon, Mar 7, 2016 at 10:29 AM, Sandro Bonazzola <<a href="mailto:sbonazzo@redhat.com">sbonazzo@redhat.com</a>> wrote:<br>
> ><br>
> ><br>
> > On Mon, Mar 7, 2016 at 9:03 AM, Martin Perina <<a href="mailto:mperina@redhat.com">mperina@redhat.com</a>> wrote:<br>
> >><br>
> >><br>
> >><br>
> >> ----- Original Message -----<br>
> >> > From: "Yaniv Bronheim" <<a href="mailto:ybronhei@redhat.com">ybronhei@redhat.com</a>><br>
> >> > To: "Martin Perina" <<a href="mailto:mperina@redhat.com">mperina@redhat.com</a>><br>
> >> > Cc: "Nir Soffer" <<a href="mailto:nsoffer@redhat.com">nsoffer@redhat.com</a>>, "Sandro Bonazzola"<br>
> >> > <<a href="mailto:sbonazzo@redhat.com">sbonazzo@redhat.com</a>>, "Francesco Romani"<br>
> >> > <<a href="mailto:fromani@redhat.com">fromani@redhat.com</a>>, "Dan Kenigsberg" <<a href="mailto:danken@redhat.com">danken@redhat.com</a>>, "devel"<br>
> >> > <<a href="mailto:devel@ovirt.org">devel@ovirt.org</a>><br>
> >> > Sent: Monday, March 7, 2016 8:16:05 AM<br>
> >> > Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning<br>
> >> > system need to be fixed<br>
> >> ><br>
> >> > I don't understand what's the different .. that's what we currently do.<br>
> >> > Sandro complains that he can't upgrade latest stable which can be<br>
> >> > 4.17.23<br>
> >> > to latest snapshot which can be 4.17.19.88 \ 4.17.19-88 - yum can't<br>
> >> > consider that as an upgrade and 4.17.19.88 can't fill HE requirement for<br>
> >> > 4.17.23<br>
> >><br>
> >> oVirt 3.6 stable release:<br>
> >> - current [1]: vdsm-4.17.23-0.el7.centos.noarch.rpm<br>
> >> - desired: vdsm-4.17.23-1.el7.centos.noarch.rpm<br>
> >><br>
> >> oVirt 3.6 stable snapshot:<br>
> >> - current [2]: vdsm-4.17.19-32.git171584b.el7.centos.noarch.rpm<br>
> >> - desired: vdsm-4.17.24-0.1.git171584b.el7.centos.noarch.rpm<br>
> >><br>
> >> oVirt master snapshot:<br>
> >> - current [3]: vdsm-4.17.999-680.gitd87d031.el7.centos.noarch.rpm<br>
> >> - desired: vdsm-4.18.0-0.680.gitd87d031.el7.centos.noarch.rpm or<br>
> >> vdsm-5.0.0-0.680.gitd87d031.el7.centos.noarch.rpm<br>
> >> (not sure what will be oVirt 4 vdsm version)<br>
> >><br>
> ><br>
> ><br>
> > +1<br>
<br>
</div></div>the down side of that is that we'd need to forsake our ability to<br>
release a new version by a mere `git tag`, and would have to include a<br>
version bump commit instead.<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><span style="font-size:12.8px"><b>Yaniv Bronhaim.</b></span><br></div></div></div></div></div>
</div>