The autopilot tests with ubuntu7~test3 are ready and looking (with unity8 and music-app flaky and could be rerun) good when compared to the stock archive results: http://people.canonical.com/~tjyrinki/qt5/ap-2015-04-09-mako-166-silo-018/. That means there's a good chance this is as good as before for Ubuntu Phone or even better, now that the KDE Plasma 5 also starts without problems too. The remaining problem are the KDE applications using deprecated behavior.
vivid-rtm should be available late next week so this could land there. Modifying the packaging to selectively patch only armhf might be an option but given vivid is <2 weeks from release even that's a bit far-fetched idea at this point. For vivid+1 that could be done so that we're not out of sync with rtm there.
The autopilot tests with ubuntu7~test3 are ready and looking (with unity8 and music-app flaky and could be rerun) good when compared to the stock archive results: http:// people. canonical. com/~tjyrinki/ qt5/ap- 2015-04- 09-mako- 166-silo- 018/. That means there's a good chance this is as good as before for Ubuntu Phone or even better, now that the KDE Plasma 5 also starts without problems too. The remaining problem are the KDE applications using deprecated behavior.
vivid-rtm should be available late next week so this could land there. Modifying the packaging to selectively patch only armhf might be an option but given vivid is <2 weeks from release even that's a bit far-fetched idea at this point. For vivid+1 that could be done so that we're not out of sync with rtm there.