<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 7, 2016 at 9:03 AM, Martin Perina <span dir="ltr"><<a href="mailto:mperina@redhat.com" target="_blank">mperina@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><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>
</span><span class="">> Cc: "Nir Soffer" <<a href="mailto:nsoffer@redhat.com">nsoffer@redhat.com</a>>, "Sandro Bonazzola" <<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" <<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 system need to be fixed<br>
><br>
</span><span class="">> 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 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>
</span>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></blockquote><div><br></div><div><br></div><div>+1</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
So if we don't get to vdsm packages versioning to the status:<br>
<br>
stable version <= stable snapshot version <= master snapshot version<br>
<br>
we can't do upgrade testing in our CI.<br>
<br>
<br>
[1] <a href="http://resources.ovirt.org/pub/ovirt-3.6/rpm/el7/noarch/" rel="noreferrer" target="_blank">http://resources.ovirt.org/pub/ovirt-3.6/rpm/el7/noarch/</a><br>
[2] <a href="http://resources.ovirt.org/pub/ovirt-3.6-snapshot/rpm/el7/noarch/" rel="noreferrer" target="_blank">http://resources.ovirt.org/pub/ovirt-3.6-snapshot/rpm/el7/noarch/</a><br>
[3] <a href="http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/noarch/" rel="noreferrer" target="_blank">http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/noarch/</a><br>
<div><div class="h5"><br>
<br>
><br>
> On Mon, Mar 7, 2016 at 7:33 AM, Martin Perina <<a href="mailto:mperina@redhat.com">mperina@redhat.com</a>> wrote:<br>
><br>
> ><br>
> ><br>
> > ----- Original Message -----<br>
> > > From: "Nir Soffer" <<a href="mailto:nsoffer@redhat.com">nsoffer@redhat.com</a>><br>
> > > To: "Martin Perina" <<a href="mailto:mperina@redhat.com">mperina@redhat.com</a>><br>
> > > Cc: "Sandro Bonazzola" <<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"<br>
> > > <<a href="mailto:danken@redhat.com">danken@redhat.com</a>>, "Yaniv Bronheim" <<a href="mailto:ybronhei@redhat.com">ybronhei@redhat.com</a>>, "devel" <<br>
> > <a href="mailto:devel@ovirt.org">devel@ovirt.org</a>><br>
> > > Sent: Sunday, March 6, 2016 6:35:53 PM<br>
> > > Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning<br>
> > system need to be fixed<br>
> > ><br>
> > > On Fri, Mar 4, 2016 at 11:28 AM, Martin Perina <<a href="mailto:mperina@redhat.com">mperina@redhat.com</a>><br>
> > wrote:<br>
> > > ><br>
> > > ><br>
> > > > ----- Original Message -----<br>
> > > >> From: "Nir Soffer" <<a href="mailto:nsoffer@redhat.com">nsoffer@redhat.com</a>><br>
> > > >> To: "Sandro Bonazzola" <<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"<br>
> > > >> <<a href="mailto:danken@redhat.com">danken@redhat.com</a>>, "Yaniv Bronheim" <<a href="mailto:ybronhei@redhat.com">ybronhei@redhat.com</a>><br>
> > > >> Cc: "devel" <<a href="mailto:devel@ovirt.org">devel@ovirt.org</a>><br>
> > > >> Sent: Friday, March 4, 2016 10:20:30 AM<br>
> > > >> Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning<br>
> > > >> system need to be fixed<br>
> > > >><br>
> > > >> On Fri, Mar 4, 2016 at 10:29 AM, Sandro Bonazzola <<br>
> > <a href="mailto:sbonazzo@redhat.com">sbonazzo@redhat.com</a> ><br>
> > > >> wrote:<br>
> > > >><br>
> > > >><br>
> > > >><br>
> > > >> Hi,<br>
> > > >> I think I already raised the issue several times, but let me raise<br>
> > this<br>
> > > >> again.<br>
> > > >> VDSM building / automated versioning is badly broken.<br>
> > > >> Currently, 3.6 snapshot is building:<br>
> > > >> vdsm-4.17.19-32.git171584b.el7.centos.src.rpm because the last tag on<br>
> > the<br>
> > > >> 3.6<br>
> > > >> branch was 4.17.19 and new tags have been created in different<br>
> > branches.<br>
> > > >> This make impossible to upgrade from stable (4.17.23) to latest<br>
> > snapshot.<br>
> > > >> This also break dependencies on other projects requiring the latest<br>
> > > >> released<br>
> > > >> version like hosted engine.<br>
> > > >><br>
> > > >> How do you suggest to version the 3.6 branch?<br>
> > > ><br>
> > > > I think we usually do something like this in other engine projects:<br>
> > > ><br>
> > > > stable released: 4.17.23-1<br>
> > > > stable snapshot: 4.17.24-0.git171584b<br>
> > > ><br>
> > > > So when new stable package is released, we will raise versions to:<br>
> > > ><br>
> > > > stable released: 4.17.24-1<br>
> > > > stable snapshot: 4.17.25-0.git171584b<br>
> > > ><br>
> > ><br>
> > > This means that snapshot version must be bumped when creating<br>
> > > a release branch, right?<br>
> ><br>
> > Yes, after release of each stable version we need also to increase<br>
> > stable snapshot version.<br>
> ><br>
> > ><br>
> > > Francesco, Yaniv, what do you think?<br>
> > ><br>
> > > Nir<br>
> > ><br>
> ><br>
><br>
><br>
><br>
> --<br>
</div></div>> *Yaniv Bronhaim.*<br>
><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Sandro Bonazzola<br>Better technology. Faster innovation. Powered by community collaboration.<br>See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a><br></div></div></div></div>
</div></div>