On Thu, Jan 30, 2014 at 11:49:42AM -0500, Adam Litke wrote: > Hi Sandro, > > After updating the MOM project's build system, I have used jenkins to > produce a set of RPMs that I would like to tag into the oVirt 3.4 > release. Please see the jenkins job [1] for the relevant artifacts > for EL6[2], F19[3], and F20[4]. > > Dan, should I submit a patch to vdsm to make it require mom >= 0.4.0? > I want to be careful to not break people's environments this late in > the 3.4 release cycle. What is the best way to minimize that damage?
Hey, we're during beta. I prefer making this requirement explicit now over having users with supervdsmd.log retate due to log spam. > > [1] http://jenkins.ovirt.org/view/All/job/manual-build-tarball/179/ > [2] > http://jenkins.ovirt.org/view/All/job/manual-build-tarball/179/label=centos6-host/artifact/exported-artifacts/mom-0.4.0-1.el6.noarch.rpm > [3] > http://jenkins.ovirt.org/view/All/job/manual-build-tarball/179/label=fedora19-host/artifact/exported-artifacts/mom-0.4.0-1.fc19.noarch.rpm > [4] > http://jenkins.ovirt.org/view/All/job/manual-build-tarball/179/label=fedora20-host/artifact/exported-artifacts/mom-0.4.0-1.fc20.noarch.rpm _______________________________________________ Engine-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/engine-devel
