BlueZ Status in Fedora.

Andreas Tunek andreas.tunek at gmail.com
Mon Aug 19 15:00:06 UTC 2013


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

I do not really understand what you mean here....

/Andreas
> --
> Richard
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20130819/1e53bd0a/attachment.html>


More information about the devel mailing list