I updated the environment to support f20, including new slave and nighlites.
i will send a separate email on it soon to infra/users/devel.
Eyal.
----- Original Message -----
From: "Doron Fediuck" <dfediuck(a)redhat.com>
To: "Dan Kenigsberg" <danken(a)redhat.com>, "David Caro Estevez"
<dcaroest(a)redhat.com>
Cc: board(a)ovirt.org, "users" <users(a)ovirt.org>, eedri(a)redhat.com,
"Sandro Bonazzola" <sbonazzo(a)redhat.com>
Sent: Thursday, November 28, 2013 1:55:13 PM
Subject: Re: Fedora 20 support, Was: [Users] oVirt Weekly Meeting Minutes -- 2013-11-27
----- Original Message -----
> From: "Dan Kenigsberg" <danken(a)redhat.com>
> To: board(a)ovirt.org, "users" <users(a)ovirt.org>
> Cc: "Doron Fediuck" <dfediuck(a)redhat.com>, eedri(a)redhat.com
> Sent: Thursday, November 28, 2013 12:19:05 PM
> Subject: Fedora 20 support, Was: [Users] oVirt Weekly Meeting Minutes --
> 2013-11-27
>
> We've forgotten to discuss an important issue: Fedora 20, which is
> expected to be out in two weeks:
>
http://fedoraproject.org/wiki/Releases/20/Schedule.
> I believe that ovirt-3.4 must support it, and that ovirt-3.3.2 would
> better do so.
>
> Toni has fixed two issues regarding Vdsm-networking, and they are going
> into ovirt-3.3.2 beta. However, we must perform much more comprehensive
> testing.
>
> We'd need to have f20 Jenkins slave(s), and someone in each team
> responsible to testing functionality. Who can cover for storage, virt,
> infra and integration?
>
> Dan.
>
Indeed so, thanks Dan.
David, is this something we have resources for?