[ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed

[Dan Kenigsberg]

On Fri, Mar 04, 2016 at 04:28:30AM -0500, Martin Perina wrote:
> 
> 
> ----- Original Message -----
> > From: "Nir Soffer" <nsoffer at redhat.com>
> > To: "Sandro Bonazzola" <sbonazzo at redhat.com>, "Francesco Romani" <fromani at redhat.com>, "Dan Kenigsberg"
> > <danken at redhat.com>, "Yaniv Bronheim" <ybronhei at redhat.com>
> > Cc: "devel" <devel at 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 at redhat.com >
> > wrote:
> > 
> > 
> > 
> > Hi,
> > I think I already raised the issue several times, but let me raise this
> > 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 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

Or alternatively, tag 4-parts versions in the 3.6.z branch, so
that raising the snapshot version can be done only once: before tagging
a new stable version, bump the snapshot version, and use 4.17.23.1 to
the stable one.