=== fvogt_vp1 is now known as fvogt_vps [08:28] mitya57: Did you want to plan a specific time to transition to 5.14.2 in Groovy? [08:28] mitya57: I ask because https://discourse.ubuntu.com/t/groovy-gorilla-release-schedule/15531 now exists and we can mark it down if we plan on doing that transition. [08:31] https://lists.qt-project.org/pipermail/releasing/2020-April/002773.html <-- maybe we can do it before 5.15.0 comes out to make it easier to do. [08:37] tsimomq2: no specific plan, but I should have Qt packaging ready in one or two weeks. [08:37] Sounds good. [08:37] Anything I can help with? I have a lot of spare time in the next few days. [08:37] Sorry, typoed in your nick [08:37] No worries. [08:38] I hope I will have qttools ready today, so you can take any submodule you want :) [08:38] Okay. :) [08:38] (In Debian experimental) [08:38] Sure. [08:39] Some submodules have merge requests from Delta-One, I will review them myself. [08:39] Sounds good to me. [08:39] Do those relate to 5.14.2? [08:39] In case tsimonq2 missed it, the only deadline I would like to meet is getting the plasma 5.19 beta in which comes out on 14th may and requires 5.14 [08:39] They are for 5.14.1, but updating to .2 should be easy. [08:39] or at least get it in a little while after [08:40] RikMills: How close to Plasma being released would you like to do that? [08:40] We can certainly meet that deadline. [08:40] (If the world doesn't explode of course, because these days that isn't necessarily a given.) [08:42] tsimonq2: there is 3 weeks between the 5.19 beta and the final release, so it doesn't 'have' to be on the dot. as long as the beta can be in to get some meaningful testing, that is fine [08:43] tsimonq2: let's not hurry and do it carefully, e.g. I usually update copyright, look at open bugs, lintian warnings, etc. [08:44] ultimately, doing the plasma beta is a preference, not a absolute need. so we can see how it goes :) [08:45] How about this: we can take our time doing Qt, and whenever that's ready, we can land Plasma in the same ticket. [08:45] Whether that happens to be at the same time as the Plasma Beta or final release. [08:45] I think it's better to land things separately. [08:45] could work, but lets decide when we have a clearer idea [08:46] yes, there is no need to have them together. it just groups more things! [08:46] and that grouping can be a PITA [08:46] ;) [08:46] Because Qt always gets entangled with other things and getting it migrate is not an easy thing. Adding Plasma won't help. [08:46] Usually I would completely agree, but in this case there are so many KDE and Plasma-related reverse-dependencies that it might be easier. Ultimately I'd say that's up to RikMills though. [08:47] not THAT many! [08:47] * tsimonq2 throws a wild PIM at RikMills [08:47] PIM is only one akonadi source to rebuild [08:48] I have no strong preference either way, to be frank. [08:48] plasma is 2 or 3. frameworks is now only 1 [08:49] as said, judgement call can be made when we start having things to land, but I think it will be better not to entangle [08:50] Fair. [08:52] tsimonq2: you still on UTC? lol [08:53] Sometimes. [08:53] In this case it's an instance of "I slept too long during the day after being up all night so I can't sleep again." [08:56] easy to happen at the moment [08:56] True. [17:56] tsimonq2: if you want to upload something during US day, good candidates are qtmultimedia, qtgraphicaleffects, qtquickcontrols2, qtcharts, qtgamepad. [17:57] These packages have 5.14.1 versions, so updating to .2 should be quite easy. [17:58] Also the first three of them are dependencies for other stuff.