----- Original Message ----- > > > > 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. And sometimes we live in this GNOME vs KDE world and then we forget all other desktops in Fedora - NM 0.9 fiasco. Where GNOME and KDE were somehow ready and everything else was released broken. So it's definitely good to talk and do it in advance. Jaroslav -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
