On 05/18/2013 05:44 PM, Dan Kenigsberg wrote:
On Sat, May 18, 2013 at 05:31:21PM -0400, Mike Burns wrote:
On 05/18/2013 05:27 PM, Dan Kenigsberg wrote:
On Fri, May 17, 2013 at 01:51:20PM -0400, Mike Burns wrote:
Hi Dan, Federico,

I noticed that the current jenkins builds of vdsm have an NVR like
vdsm-4.10.3-0.xxxxxx while the current stable version is
4.10.3-10.xxxxx.  This means that someone testing nightly builds for
oVirt 3.3 will always get the stable version from either ovirt.org
or Fedora repos, and not the nightly build.

I would submit a patch to increase the NVR, but I don't know which
change is the right one (vdsm-4.10.4 or vdsm-4.11.0 or vdsm-5.0.0).

oVirt-3.3 would carry at least vdsm-4.11.0, so you could use that NV as
a base for nightly builds.

If you can wait, I hope that within a week, we will tag the master
branch with v4.11.0. I practically waiting for Vinzenz's little vm.py
refactoring for that to happen.

Can we maybe just push a patch that bumps the NVR to 4.10.3-999 or
something that is the newer than the current stable?  Then when you
tag 4.11.0, you can update then as well.

The current state is that people could not test the latest vdsm from
git unless they manually install the exact version.

We can easily add a 4.10.4 tag. But wouldn't it be just as easy (and
maybe a bit less confusing) to do the -999 trick on the nightly build

I don't really know.

Eyal, Can you look into this? I don't really know the vdsm build job (or process).

vdsm-devel mailing list

Reply via email to