Re: [SailfishDevel] Qt 5.2 in devel
2014-07-07 23:37 GMT+03:00 Robin Burchell : > On the bright side, I¹m fairly confident that future upgrades will be less > painful, as part of the pain was also on our side in that we rushed a few > things to get to market last year, and we paid the price in doing that > work properly. I'd also say it's probable. Ubuntu had a similar huge stabilizing/patching/backporting period with Qt 5.2.1 earlier for its phone/tablet images, but everything was upstreamed to 5.3.0+. Now 5.3 has seemed great without too many patches and it was much easier switch than to 5.2.1 (added with ~60 patches). But I wouldn't ever consider doing two steps at once for a product that is in customers' hands, and a heavily patched 5.2 will bring a lot of the benefits of 5.3 anyway. My feeling is that the biggest growing pains for this kind of system wide extensive Qt 5 usage are now resolved, thanks to efforts from all parties involved. I hope 5.4 and onwards won't break anything big :) -Timo ps. I'm using this opportunity to thanks for Tahkalampi, awesome release! ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Qt 5.2 in devel
On Monday 07 July 2014 20:37 Robin Burchell wrote: > This might sound strange and all, but do realize that we are probably one > of the most extensive users of the Qt stack (in that we literally use > pretty much all of it) and certainly one of the most extensive users of > QtQuick & QML. We¹re a pretty good stress-test for finding corner cases, > so we need to be careful. Next to KDE Frameworks 5 :) Not officially released yet though. -- Med venlig hilsen / Best Regards Thomas Tanghus ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Qt 5.2 in devel
Den 07.07.14 20:12 skrev "Timur Kristóf" : >Why just 5.2? Why not go straight to 5.3? Gunnar already answered this, but I¹ll repeat it somewhat: We¹ve put a reasonable amount of work into stabilizing 5.2, and are fairly confident that it¹s of acceptable quality by now. Pushing any change into that has an inherent risk of regression (I can say certainly say that we found more than our fair share of bugs along the way during this upgrade, and are still running into some new ones from time to timeŠ :)) That doesn¹t mean further upgrades won¹t happen in the future, it just means they won¹t happen immediately. When precisely they happen will depend on when we can spare effort to it (which in turn depends on what benefits we get out of itŠ) and the quality of the upstream releases. This might sound strange and all, but do realize that we are probably one of the most extensive users of the Qt stack (in that we literally use pretty much all of it) and certainly one of the most extensive users of QtQuick & QML. We¹re a pretty good stress-test for finding corner cases, so we need to be careful. On the bright side, I¹m fairly confident that future upgrades will be less painful, as part of the pain was also on our side in that we rushed a few things to get to market last year, and we paid the price in doing that work properly. BR, Robin ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Qt 5.2 in devel
Why just 5.2? Why not go straight to 5.3? On Wed, Jun 18, 2014 at 5:10 AM, Robin Burchell wrote: > Hello intrepid developers, > > Qt 5.2 rebuilds have (finally, thank god) finished in devel. I’ve > updated a single device (via version —dup) so far without too many ill > effects (see below), and done some brief smoke testing. The device rebooted > the user session successfully, and rebooted to a UI OK, applications start, > and at a very light play, they appear to be in reasonable shape. > > The one symptom of bad behavior I’ve seen so far is that orientation > does not appear to work (at least once), this appears to be a hardware > adaptation problem: /system/bin/sensord was not running on reboot. > Rebooting again made it appear. > > There are some rough edges, but nothing apparently life threatening: > >- Gunnar, can you please remove the v8 dependency from the scene graph >adaptation plugin? >- Bernd, can you please remove cutes-qt5 from sailfish-version (and >remove cutes-qt5 from the repos)? I guess there’s nothing else requiring it >after backup’s removal of it (Denis/Giulio, can you help out with anything >needed here?) >- Cor appears to be failing to build on ARM in devel. I don’t think >this is related to Qt, but needs checking. Denis? > > Developers: please upgrade your devices *with some caution* and see how > your areas look. > > I’m going to head to bed now. If problems occur, if it isn’t urgent, > file it in bugzilla, and add the Qt5.2 keyword & CC me. If it is urgent, > please try pretend that it isn’t until I’m around again, or alternatively, > you can (try to) call me on +47 9059 2624. If you’re lucky, I may even > leave the phone off silent :). > > BR, > Robin > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Qt 5.2 in devel
On 21 Jun 2014, at 19:54, Tone Kastlunger wrote: > Hi, > great job! > It would be amazing to get a (link to a ) list of features coming with this > release of qt to jolla. A more complete list will be compiled when we're about to release. For the Qt bits, at least everything from qtbase and qtdeclarative in: http://qt-project.org/wiki/New-Features-in-Qt-5.2 and more in-depth changes files: https://qt.gitorious.org/qt/qtbase/source/4cb03924c113c74b99e18c7347278600a011e917:dist/changes-5.2.0 https://qt.gitorious.org/qt/qtbase/source/4cb03924c113c74b99e18c7347278600a011e917:dist/changes-5.2.1 https://qt.gitorious.org/qt/qtdeclarative/source/d757806537a1e7233bd656e4d2170cfa994d9d44:dist/changes-5.2.0 http://qt.gitorious.org/qt/qtdeclarative/source/d757806537a1e7233bd656e4d2170cfa994d9d44:dist/changes-5.2.1 cheers, Gunnar > > Best, > tortoisedoc > > > On Sat, Jun 21, 2014 at 7:48 PM, Gunnar Sletta > wrote: > > On 21 Jun 2014, at 16:21, Alejandro Exojo wrote: > > > El Wednesday 18 June 2014, Robin Burchell escribió: > >> Sorry folks. This wasn’t intended to be posted here, but, have a slight > >> visual on what’s going on behind the curtain anyway. :) > > > > I hope everything went well and nobody phoned you in the middle of sleep. :) > > > >> tl;dr: Qt 5.2 upgrade is on the way in the nearish (but not immediate) > >> future > > > > How come that you are not skipping 5.2 and going straight to 5.3? > > Hi Alejandro, > > Moving to a new Qt release takes quite a bit of effort and our 5.2 branch is > getting into a pretty good shape. Jumping to 5.3 would mean a lot of > additional sanity testing and based on the outcome of that, adapting to > changes and bug fixing. It would delay the update by an unknown amount of > weeks or months. The 5.2 branch already contains stuff which we really want > in the platform (like the improvements to QtQuick) and we want those sooner > rather than later. We'll get around to 5.3 and also 5.4 eventually, though. > Just not right now :) > > > IIRC, you > > had some patches on top of 5.1, so I understand that rebasing them is a lot > > of > > work. Skipping a release might be harder now, but maybe is worth it later > > on. > > Very true, an we've taken steps to get away from that situation. For our Qt > 5.2 branch, we still have a lot of patches, but all of these patches were > upstreamed to 5.3 and 5.4 before they were back-ported into our 5.2 branch, > so we're converging rather than diverging. > > > I'm pretty sure you know what you are doing, but I fear you might end up > > with > > non-upstreamed things and end up with the problem the SDK has, that is some > > releases behind what Qt Creator is upstream, for example. > > It is a valid point, and do we want to stay fairly close to the latest > released Qt, preferably without patches. But since we also have a platform on > top of Qt, there is some latency in getting there. > > Hope that answers your question. > > cheers, > Gunnar > > > > > Cheers. > > > > -- > > Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2 > > http://barnacity.net/ | http://disperso.net > > ___ > > SailfishOS.org Devel mailing list > > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Qt 5.2 in devel
El Saturday 21 June 2014, Gunnar Sletta escribió: > Very true, an we've taken steps to get away from that situation. For our Qt > 5.2 branch, we still have a lot of patches, but all of these patches were > upstreamed to 5.3 and 5.4 before they were back-ported into our 5.2 > branch, so we're converging rather than diverging. Awesome, that's what I wanted to read. :-) > It is a valid point, and do we want to stay fairly close to the latest > released Qt, preferably without patches. But since we also have a platform > on top of Qt, there is some latency in getting there. Yes, I completely understand, it also happened to me. I have a couple of projects at work where we use 5.2, and I had to override Qt's behaviour (for simple stuff like logging to the journal and configuring logging categories in a file) using the public API. That was simple, but the cool, mantainable way is of course adding the feature in Qt itself so all applications have it automatically. We didn't had the time, but luckily Robin and Kai added those exact two features to 5.3, so we can get rid of our custom code. > Hope that answers your question. Definetely. And let us know if there is some way to help with these kind of things. Greetings. -- Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2 http://barnacity.net/ | http://disperso.net ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Qt 5.2 in devel
Hi, great job! It would be amazing to get a (link to a ) list of features coming with this release of qt to jolla. Best, tortoisedoc On Sat, Jun 21, 2014 at 7:48 PM, Gunnar Sletta wrote: > > On 21 Jun 2014, at 16:21, Alejandro Exojo wrote: > > > El Wednesday 18 June 2014, Robin Burchell escribió: > >> Sorry folks. This wasn’t intended to be posted here, but, have a slight > >> visual on what’s going on behind the curtain anyway. :) > > > > I hope everything went well and nobody phoned you in the middle of > sleep. :) > > > >> tl;dr: Qt 5.2 upgrade is on the way in the nearish (but not immediate) > >> future > > > > How come that you are not skipping 5.2 and going straight to 5.3? > > Hi Alejandro, > > Moving to a new Qt release takes quite a bit of effort and our 5.2 branch > is getting into a pretty good shape. Jumping to 5.3 would mean a lot of > additional sanity testing and based on the outcome of that, adapting to > changes and bug fixing. It would delay the update by an unknown amount of > weeks or months. The 5.2 branch already contains stuff which we really want > in the platform (like the improvements to QtQuick) and we want those sooner > rather than later. We'll get around to 5.3 and also 5.4 eventually, though. > Just not right now :) > > > IIRC, you > > had some patches on top of 5.1, so I understand that rebasing them is a > lot of > > work. Skipping a release might be harder now, but maybe is worth it > later on. > > Very true, an we've taken steps to get away from that situation. For our > Qt 5.2 branch, we still have a lot of patches, but all of these patches > were upstreamed to 5.3 and 5.4 before they were back-ported into our 5.2 > branch, so we're converging rather than diverging. > > > I'm pretty sure you know what you are doing, but I fear you might end up > with > > non-upstreamed things and end up with the problem the SDK has, that is > some > > releases behind what Qt Creator is upstream, for example. > > It is a valid point, and do we want to stay fairly close to the latest > released Qt, preferably without patches. But since we also have a platform > on top of Qt, there is some latency in getting there. > > Hope that answers your question. > > cheers, > Gunnar > > > > > Cheers. > > > > -- > > Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2 > > http://barnacity.net/ | http://disperso.net > > ___ > > SailfishOS.org Devel mailing list > > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Qt 5.2 in devel
On 21 Jun 2014, at 16:21, Alejandro Exojo wrote: > El Wednesday 18 June 2014, Robin Burchell escribió: >> Sorry folks. This wasn’t intended to be posted here, but, have a slight >> visual on what’s going on behind the curtain anyway. :) > > I hope everything went well and nobody phoned you in the middle of sleep. :) > >> tl;dr: Qt 5.2 upgrade is on the way in the nearish (but not immediate) >> future > > How come that you are not skipping 5.2 and going straight to 5.3? Hi Alejandro, Moving to a new Qt release takes quite a bit of effort and our 5.2 branch is getting into a pretty good shape. Jumping to 5.3 would mean a lot of additional sanity testing and based on the outcome of that, adapting to changes and bug fixing. It would delay the update by an unknown amount of weeks or months. The 5.2 branch already contains stuff which we really want in the platform (like the improvements to QtQuick) and we want those sooner rather than later. We'll get around to 5.3 and also 5.4 eventually, though. Just not right now :) > IIRC, you > had some patches on top of 5.1, so I understand that rebasing them is a lot > of > work. Skipping a release might be harder now, but maybe is worth it later on. Very true, an we've taken steps to get away from that situation. For our Qt 5.2 branch, we still have a lot of patches, but all of these patches were upstreamed to 5.3 and 5.4 before they were back-ported into our 5.2 branch, so we're converging rather than diverging. > I'm pretty sure you know what you are doing, but I fear you might end up with > non-upstreamed things and end up with the problem the SDK has, that is some > releases behind what Qt Creator is upstream, for example. It is a valid point, and do we want to stay fairly close to the latest released Qt, preferably without patches. But since we also have a platform on top of Qt, there is some latency in getting there. Hope that answers your question. cheers, Gunnar > > Cheers. > > -- > Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2 > http://barnacity.net/ | http://disperso.net > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Qt 5.2 in devel
El Wednesday 18 June 2014, Robin Burchell escribió: > Sorry folks. This wasn’t intended to be posted here, but, have a slight > visual on what’s going on behind the curtain anyway. :) I hope everything went well and nobody phoned you in the middle of sleep. :) > tl;dr: Qt 5.2 upgrade is on the way in the nearish (but not immediate) > future How come that you are not skipping 5.2 and going straight to 5.3? IIRC, you had some patches on top of 5.1, so I understand that rebasing them is a lot of work. Skipping a release might be harder now, but maybe is worth it later on. I'm pretty sure you know what you are doing, but I fear you might end up with non-upstreamed things and end up with the problem the SDK has, that is some releases behind what Qt Creator is upstream, for example. Cheers. -- Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2 http://barnacity.net/ | http://disperso.net ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Qt 5.2 in devel
On Wednesday 18 June 2014 06:10:06 Robin Burchell wrote: > Hello intrepid developers, > > Qt 5.2 rebuilds have (finally, thank god) finished in devel. I’ve updated a > single device (via version —dup) so far without too many ill effects (see > below), and done some brief smoke testing. The device rebooted the user > session successfully, and rebooted to a UI OK, applications start, and at a > very light play, they appear to be in reasonable shape. > > The one symptom of bad behavior I’ve seen so far is that orientation does > not appear to work (at least once), this appears to be a hardware > adaptation problem: /system/bin/sensord was not running on reboot. > Rebooting again made it appear. > > There are some rough edges, but nothing apparently life threatening: > Gunnar, can you please remove the v8 dependency from the scene graph > adaptation plugin? Bernd, can you please remove cutes-qt5 from > sailfish-version (and remove cutes-qt5 from the repos)? I guess there’s > nothing else requiring it after backup’s removal of it (Denis/Giulio, can do not remove cutes from repos, I will update the version, taking it from next. > you help out with anything needed here?) Cor appears to be failing to build > on ARM in devel. I don’t think this is related to Qt, but needs checking. > Denis? Developers: please upgrade your devices with some caution and see > how your areas look. https://build.jollamobile.com/package/show?package=cor&project=nemo%3Amw it looks like cor is built fine or am I missing smth.? also the same is for next: https://build.jollamobile.com/package/show?package=cor&project=nemo%3Amw%3Anext - denis > > I’m going to head to bed now. If problems occur, if it isn’t urgent, file it > in bugzilla, and add the Qt5.2 keyword & CC me. If it is urgent, please try > pretend that it isn’t until I’m around again, or alternatively, you can > (try to) call me on +47 9059 2624. If you’re lucky, I may even leave the > phone off silent :). > > BR, > Robin ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] Qt 5.2 in devel
Sorry folks. This wasn’t intended to be posted here, but, have a slight visual on what’s going on behind the curtain anyway. :) tl;dr: Qt 5.2 upgrade is on the way in the nearish (but not immediate) future :) Fra: Robin Burchell mailto:robin.burch...@jolla.com>> Svar til: Sailfish OS Developers mailto:devel@lists.sailfishos.org>> Dato: onsdag 18. juni 2014 05:10 Til: Bernd Wachter mailto:bernd.wach...@jolla.com>>, Gunnar Sletta mailto:gunnar.sle...@jolla.com>>, Denis Zalevskiy mailto:denis.zalevs...@jolla.com>>, Giulio Camuffo mailto:giulio.camu...@jolla.com>> Kopi: Sailfish OS Developers mailto:devel@lists.sailfishos.org>> Emne: [SailfishDevel] Qt 5.2 in devel Hello intrepid developers, Qt 5.2 rebuilds have (finally, thank god) finished in devel. I’ve updated a single device (via version —dup) so far without too many ill effects (see below), and done some brief smoke testing. The device rebooted the user session successfully, and rebooted to a UI OK, applications start, and at a very light play, they appear to be in reasonable shape. The one symptom of bad behavior I’ve seen so far is that orientation does not appear to work (at least once), this appears to be a hardware adaptation problem: /system/bin/sensord was not running on reboot. Rebooting again made it appear. There are some rough edges, but nothing apparently life threatening: * Gunnar, can you please remove the v8 dependency from the scene graph adaptation plugin? * Bernd, can you please remove cutes-qt5 from sailfish-version (and remove cutes-qt5 from the repos)? I guess there’s nothing else requiring it after backup’s removal of it (Denis/Giulio, can you help out with anything needed here?) * Cor appears to be failing to build on ARM in devel. I don’t think this is related to Qt, but needs checking. Denis? Developers: please upgrade your devices with some caution and see how your areas look. I’m going to head to bed now. If problems occur, if it isn’t urgent, file it in bugzilla, and add the Qt5.2 keyword & CC me. If it is urgent, please try pretend that it isn’t until I’m around again, or alternatively, you can (try to) call me on +47 9059 2624. If you’re lucky, I may even leave the phone off silent :). BR, Robin ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org<mailto:devel-unsubscr...@lists.sailfishos.org> ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] Qt 5.2 in devel
Hello intrepid developers, Qt 5.2 rebuilds have (finally, thank god) finished in devel. I’ve updated a single device (via version —dup) so far without too many ill effects (see below), and done some brief smoke testing. The device rebooted the user session successfully, and rebooted to a UI OK, applications start, and at a very light play, they appear to be in reasonable shape. The one symptom of bad behavior I’ve seen so far is that orientation does not appear to work (at least once), this appears to be a hardware adaptation problem: /system/bin/sensord was not running on reboot. Rebooting again made it appear. There are some rough edges, but nothing apparently life threatening: * Gunnar, can you please remove the v8 dependency from the scene graph adaptation plugin? * Bernd, can you please remove cutes-qt5 from sailfish-version (and remove cutes-qt5 from the repos)? I guess there’s nothing else requiring it after backup’s removal of it (Denis/Giulio, can you help out with anything needed here?) * Cor appears to be failing to build on ARM in devel. I don’t think this is related to Qt, but needs checking. Denis? Developers: please upgrade your devices with some caution and see how your areas look. I’m going to head to bed now. If problems occur, if it isn’t urgent, file it in bugzilla, and add the Qt5.2 keyword & CC me. If it is urgent, please try pretend that it isn’t until I’m around again, or alternatively, you can (try to) call me on +47 9059 2624. If you’re lucky, I may even leave the phone off silent :). BR, Robin ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
