On Mon, Mar 02, 2015 at 08:46:51AM +0100, Sandro Bonazzola wrote:
> Il 27/02/2015 23:43, Dan Kenigsberg ha scritto:
>> On Fri, Feb 27, 2015 at 03:48:22PM -0500, Nir Soffer wrote:
>>> ----- Original Message -----
>>>> From: "Nir Soffer" <nsoffer(a)redhat.com>
>>>> To: "Sandro Bonazzola" <sbonazzo(a)redhat.com>
>>>> Cc: announce(a)ovirt.org, Users(a)ovirt.org, devel(a)ovirt.org
>>>> Sent: Friday, February 27, 2015 10:35:52 PM
>>>> Subject: Re: [ovirt-users] [ovirt-devel] [ANN] oVirt 3.5.2 First
Release Candidate is now available for testing
>>>>
>>>> ----- Original Message -----
>>>>> From: "Sandro Bonazzola" <sbonazzo(a)redhat.com>
>>>>> To: announce(a)ovirt.org, devel(a)ovirt.org, Users(a)ovirt.org
>>>>> Sent: Friday, February 27, 2015 12:00:10 PM
>>>>> Subject: [ovirt-devel] [ANN] oVirt 3.5.2 First Release Candidate is
now
>>>>> available for testing
>>>>>
>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> Hash: SHA1
>>>>>
>>>>> The oVirt team is pleased to announce that the 3.5.2 First Release
>>>>> Candidate
>>>>> is now
>>>>> available for testing as of Feb 27th 2015.
>>>>>
>>>>> The release candidate is available now for Fedora 20...
>>>>
>>>> Do we support Fedora 21?
>>
>> I don't recall a formal statement about it, but I surely WANT to support
>> it, as nowadays it is the run-of-the-mill Fedora version.
>
> Please be sure that all relevant rpms for VDSM Fedora 21 support are published in
ovirt-3.5-snapshot.
> Latest job run
is:http://jenkins.ovirt.org/view/Publishers/job/publish_ovirt_rpms_nightl...
Important point in deed: no Vdsm build is there or in
http://resources.ovirt.org/pub/ovirt-3.5-snapshot/rpm/fc21/noarch/
What should be done to enabled f21 builds of Vdsm?
change the vdsm build job for 3.5 in order to make it building for fedora 21 too (yaml
code in jenkins repo)
change the publisher job for 3.5 in order to publish the artifacts from the fedora 21 vdsm
build job (manual change in jenkins job, not yet migrated
to yaml)
Same for all the vdsm deps.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at