<p dir="ltr"><br>
On 19/08/2013 4:31 PM, "Richard Vickery" <<a href="mailto:richard.vickeryrv@gmail.com">richard.vickeryrv@gmail.com</a>> wrote:<br>
><br>
> On Sun, Aug 18, 2013 at 8:03 PM, Matthew Garrett <<a href="mailto:mjg59@srcf.ucam.org">mjg59@srcf.ucam.org</a>> wrote:<br>
> > On Sun, Aug 18, 2013 at 02:28:34PM -0700, Ryan Rix wrote:<br>
> ><br>
> >> Basically we ship Fedora 20 in a state where one only of our major desktop<br>
> >> environments supports bluetooth in a stable fashion? That seems kind of like a<br>
> >> disaster waiting to happen.<br>
> ><br>
> > The current release blocking desktops are Gnome and KDE. If those are<br>
> > broken then F20 doesn't ship - if they're working, it ships. It'd be<br>
> > unfortunate to ship a release that doesn't support the non-blocking<br>
> > desktops, but (right now) it's fundamentally up to them to provide the<br>
> > development effort to ensure that they have a full feature set.<br>
> ><br>
> > --<br>
> > Matthew Garrett | <a href="mailto:mjg59@srcf.ucam.org">mjg59@srcf.ucam.org</a><br>
> > --<br>
><br>
> Instead of shipping it, is there a problem with giving it to those on<br>
> the developer list and letting us iron out the kinks?<br>
></p>
<p dir="ltr">I do not really understand what you mean here....</p>
<p dir="ltr">/Andreas<br>
> --<br>
> Richard<br>
> --<br>
> devel mailing list<br>
> <a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
> <a href="https://admin.fedoraproject.org/mailman/listinfo/devel">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
> Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct">http://fedoraproject.org/code-of-conduct</a></p>