[ovirt-devel] [URGENT][ACTION REQUIRED] vdsm versioning system need to be fixed
Nir Soffer
nsoffer at redhat.com
Fri Mar 4 09:20:30 UTC 2016
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
> <http://jenkins.ovirt.org/job/vdsm_3.6_build-artifacts-el7-x86_64/178/artifact/exported-artifacts/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?
Nir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20160304/42d8bead/attachment-0001.html>
More information about the Devel
mailing list