<div dir="ltr">I don't understand what's the different .. that's what we currently do. Sandro complains that he can't upgrade latest stable which can be 4.17.23 to latest snapshot which can be 4.17.19.88 \ 4.17.19-88 - yum can't consider that as an upgrade and 4.17.19.88 can't fill HE requirement for 4.17.23 </div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 7, 2016 at 7:33 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: "Nir Soffer" <<a href="mailto:nsoffer@redhat.com">nsoffer@redhat.com</a>><br>
</span><div><div class="h5">> 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" <<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" <<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 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>> 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 < <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 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 the<br>
> >> 3.6<br>
> >> branch was 4.17.19 and new tags have been created in different branches.<br>
> >> This make impossible to upgrade from stable (4.17.23) to latest 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>
</div></div>Yes, after release of each stable version we need also to increase<br>
stable snapshot version.<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> Francesco, Yaniv, what do you think?<br>
><br>
> Nir<br>
><br>
</div></div></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>