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