Re: Fedora 21 Final blocker bug status report #1

2014-11-23 Thread Cole Robinson
On 11/22/2014 12:15 AM, Adam Williamson wrote: Hi folks! We're now into the Fedora 21 Final freeze period, and we really need to address blocker bugs promptly to try and make the scheduled release date. On the current schedule Go/No-Go will happen on 2014-12-04, which means we really need the fin

Re: Fedora 21 Final blocker bug status report #1

2014-11-22 Thread M. Edward (Ed) Borasky
Got it - karma given ;-) On Sat, Nov 22, 2014 at 12:26 PM, M. Edward (Ed) Borasky wrote: > downloading now > > On Sat, Nov 22, 2014 at 4:52 AM, Patrick Laimbock > wrote: > >> On 22-11-14 07:25, M. Edward (Ed) Borasky wrote: >> >>> I'll volunteer to test >>> https://bugzilla.redhat.com/show_bug.

Re: Fedora 21 Final blocker bug status report #1

2014-11-22 Thread M. Edward (Ed) Borasky
downloading now On Sat, Nov 22, 2014 at 4:52 AM, Patrick Laimbock wrote: > On 22-11-14 07:25, M. Edward (Ed) Borasky wrote: > >> I'll volunteer to test >> https://bugzilla.redhat.com/show_bug.cgi?id=1146232 "f21 workstation >> ships 'default' network, so loses connectivity when run in a VM" - >>

Re: Fedora 21 Final blocker bug status report #1

2014-11-22 Thread Patrick Laimbock
On 22-11-14 07:25, M. Edward (Ed) Borasky wrote: I'll volunteer to test https://bugzilla.redhat.com/show_bug.cgi?id=1146232 "f21 workstation ships 'default' network, so loses connectivity when run in a VM" - libvirt / gnome-boxes - when do we expect TC3? The various iso images can be found here

Re: Fedora 21 Final blocker bug status report #1

2014-11-21 Thread M. Edward (Ed) Borasky
I'll volunteer to test https://bugzilla.redhat.com/show_bug.cgi?id=1146232 "f21 workstation ships 'default' network, so loses connectivity when run in a VM" - libvirt / gnome-boxes - when do we expect TC3? On Fri, Nov 21, 2014 at 9:15 PM, Adam Williamson wrote: > Hi folks! We're now into the Fed

Fedora 21 Final blocker bug status report #1

2014-11-21 Thread Adam Williamson
Hi folks! We're now into the Fedora 21 Final freeze period, and we really need to address blocker bugs promptly to try and make the scheduled release date. On the current schedule Go/No-Go will happen on 2014-12-04, which means we really need the final release candidate built by 2014-12-02, so even