On Thu, 2015-01-08 at 08:54 -0500, Bastien Nocera wrote: > > ----- Original Message ----- > <snip> > > Thanks, Hans. We wanted to make sure that we didn't have another > > instance of the bluetooth fiasco from a couple releases ago, where GNOME > > changed the Bluetooth stack and broke things underneath KDE. If this is > > already addressed (or at least irrelevant), that's perfect. > > BlueZ 5.0, released december 2012. > GNOME with BlueZ 5 support, september 2013. > Fedora 20 with BlueZ 5 included, december 2013. Was it really only F20? Seems older than that. Anyway, it's irrelevant when BlueZ landed upstream. What went wrong was that GNOME landed the support which broke backwards compatibility, which forced KDE to scramble to get it working on their side. This was a communication issue, and I think everyone would prefer not to repeat it. My apologies if my original message bringing it up sounded accusatory. It was not my intent. The whole point of System Wide Changes is to ensure that all the people who might be impacted by a Change are notified and involved. So in order to avoid forcing sudden and unexpected work on a particular group, we called it out as a contingency issue: if either or both of the release-blocking desktops don't make the contingency deadlines, it gets deferred so they can both get it right in the next release.
Attachment:
signature.asc
Description: This is a digitally signed message part
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
