Hi, The report was marked as a P2, and nobody raised it to be a showstopper for the release. Trying to do this on the day before is unfair to everybody else.
I understand that this is an issue for KDE, but since it only happens when using qDBusAddSpyHook I am convinced it’ll hit almost no other user. So while KDE is important, I don’t think this is a good enough reason to block the release. It’s been taking too long in any case already. Let’s rather get this fixed in the 5.6 branch and follow up with a 5.6.1 quickly. We have other important bug fixes already waiting in that branch as well. Cheers, Lars On 15/03/16 07:35, "Development on behalf of Sune Vuorela" <[email protected] on behalf of [email protected]> wrote: >> >> TBUG-51676 seems to be p2 and so on cannot block the release. It also have >> been open a while without anyone indicating it should be fixed before >> releasing so I wouldn't block the release because of this at this point >> anymore. I think adding this in known issues page >> (https://wiki.qt.io/Qt_5.6.0_Known_Issues) & fixing this in 5.6.1 should be >> ok even this is regression issue >> > >If it is reliably deadlocking on launch of KDE Desktop, then P2 is too >low. > >What the KDE people does with Qt is one of the biggest public show-offs >of what can be done with Qt technoloy. We should not undermine that. > >/Sune >Qt Contributor >KDE Developer >Debian Developer > >_______________________________________________ >Development mailing list >[email protected] >http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
