On Mon, Mar 07, 2016 at 12:06:32PM +0200, Nir Soffer wrote:
+1
On Mon, Mar 7, 2016 at 10:29 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
On Mon, Mar 7, 2016 at 9:03 AM, Martin Perina <mperina@redhat.com> wrote:
----- Original Message -----
From: "Yaniv Bronheim" <ybronhei@redhat.com> To: "Martin Perina" <mperina@redhat.com> Cc: "Nir Soffer" <nsoffer@redhat.com>, "Sandro Bonazzola" <sbonazzo@redhat.com>, "Francesco Romani" <fromani@redhat.com>, "Dan Kenigsberg" <danken@redhat.com>, "devel" <devel@ovirt.org> Sent: Monday, March 7, 2016 8:16:05 AM Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed
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
oVirt 3.6 stable release: - current [1]: vdsm-4.17.23-0.el7.centos.noarch.rpm - desired: vdsm-4.17.23-1.el7.centos.noarch.rpm
oVirt 3.6 stable snapshot: - current [2]: vdsm-4.17.19-32.git171584b.el7.centos.noarch.rpm - desired: vdsm-4.17.24-0.1.git171584b.el7.centos.noarch.rpm
oVirt master snapshot: - current [3]: vdsm-4.17.999-680.gitd87d031.el7.centos.noarch.rpm - desired: vdsm-4.18.0-0.680.gitd87d031.el7.centos.noarch.rpm or vdsm-5.0.0-0.680.gitd87d031.el7.centos.noarch.rpm (not sure what will be oVirt 4 vdsm version)
+1
the down side of that is that we'd need to forsake our ability to release a new version by a mere `git tag`, and would have to include a version bump commit instead.