15:08:17 #startmeeting KDE SIG Meeting 15:08:17 Meeting started Tue Mar 5 15:08:17 2013 UTC. The chair is Kevin_Kofler. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:08:17 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:08:24 #meetingname kde-sig 15:08:24 The meeting name has been set to 'kde-sig' 15:08:30 #topic Roll Call 15:08:32 o/ 15:08:44 Who's present? 15:09:12 * mbriza 's present although won't participate very much 15:09:33 yo 15:09:38 * rnovacek is here 15:09:41 * ltinkl is here 15:09:45 * jgrulich is present 15:10:05 * than is present 15:10:38 jreznik: Ping? 15:10:49 * Martix_ is here 15:10:50 * jreznik is here 15:11:46 #chair tdfischer mbriza rdieter rnovacek ltinkl jgrulich than Martix jreznik 15:11:46 Current chairs: Kevin_Kofler Martix jgrulich jreznik ltinkl mbriza rdieter rnovacek tdfischer than 15:12:07 #info Kevin_Kofler, tdfischer, mbriza, rdieter, rnovacek, ltinkl, jgrulich, than, Martix, jreznik present. 15:12:13 #topic Agenda 15:12:20 So, what's there to discuss? 15:12:33 I suppose we don't have a wiki page yet again, do we? 15:12:44 4.10.1 status 15:12:46 kde-4.10/f18 status, kde-4.10 for f17 (to do or not) 15:13:10 Kevin_Kofler: thanks, I'm just poking around, randomly visited this IRC tab, but I start working tomorrow on KDE 4.10 Test Day: https://fedoraproject.org/wiki/Test_Day:2013-03-14_KDE_4.10 15:13:16 yes, decision for 17 update 15:13:31 Let's start with the status report, and then we can talk about F17. 15:13:37 ok 15:13:41 #topic 4.10.1 status (Rawhide, F18) 15:14:12 so rawhide is done, f18-kde koji target builds are done and in kde-unstable repo (since ~12 hrs ago) 15:14:44 all that merging is ... time-consuming 15:15:37 anyway, that's all i have, can prepare a f18 bodhi update sometime soon 15:16:05 #info rawhide is done, f18-kde koji target builds are done and in kde-unstable repo (since ~12 hrs ago 15:16:22 #info rdieter can prepare a f18 bodhi update sometime soon 15:16:42 probably will move stuff to kde-testing prior to bodhi 15:16:53 nucleo reported some issues with 4.10.1, but they don't seem to be reproducible. :-( 15:17:31 There was also a report on the mailing list from Harald Reindl about 4.10.x messing up his plasmoids, has nobody else encountered that? 15:17:40 right, particularly that plasma didn't start up cleaning on first install after upgrade 15:17:52 s/cleaning/cleanly/ 15:18:02 I wonder if it's related to ihatethecashew, is anybody (other than him and me) using that? 15:18:07 (I haven't tried 4.10 yet.) 15:18:14 Kevin_Kofler: no, I assume that's why there isn't any followup 15:19:03 I think we should test it with ihatethecashew then, maybe then we can reproduce it. 15:19:20 drop ihatethecashew :) 15:19:23 It might be that ihatethecashew is misbehaving with the changed internals in 4.10 (QMLization). 15:19:35 ihatethesuggestionofdroppingihatethecashew ;-) 15:21:18 seriously though, everyone should be thoroughly testing all their favorite plasma bits 15:22:07 Looks like upstream is dead, it has been deleted from kde-look.org. :-( 15:22:13 * than installed ihatethecashew 15:22:39 it works fine here 15:23:09 than: probably need to restart your session, the problems all happened on startup 15:23:27 ah ok, i will try it later 15:24:50 move on to f17/kde-4.10 ? 15:26:02 #topic 4.10 for Fedora 17 15:26:28 * rdieter asked for more feedback onlist, got one more positive reply 15:27:33 i have installed 4.10 on my f17 machine 15:27:48 I guess i'm tenatively on board with moving forward on f17 too, it'll be a lot of work (again) to merge all the git branches, but I think it'll be worth it too 15:28:10 update from 4.9.5 to 4.10 works withhout any problem 15:28:15 when/if this happens again, will leave the merging task to someone else. :) 15:28:22 I am also using 4.10.0 on F17 15:28:28 I'm for it too, I've always been in favor of doing those upgrades. :-) 15:28:37 works the same as in S18 15:28:43 rdieter: i can take care of it :) 15:29:12 jreznik: ? I recall you and me were the only ones last week not 100% behind the idea, how about now? 15:30:56 jreznik: your vote please :) 15:33:10 sorry 15:33:12 * jreznik is back 15:34:03 I'm not convinced to do it and even more -1, but consider me 0 - I'm not going to block it 15:34:47 * rdieter is 0 too 15:35:21 but please, be careful :) 15:35:53 kde repo is probably better option for everyone who really wants 4.10 on f17 15:37:16 you can push 4.10 to f17-updates-testing only and let users test it first next Thursday 15:37:47 Martix: If we move forward, it will definitely sit in updates-testing for awhile 15:37:47 and if something bad happen, drop it from updates 15:37:57 not to be rushed 15:38:13 It'll definitely go through testing, we're not going to cheat with the karma and IMHO we should disable autokarma entirely. 15:38:21 rdieter: ok, I'm not familliar with your updating schedule :-) 15:38:49 But of course the plan is to go stable eventually, testing is not a dumping ground for crap that will never go stable. 15:38:56 (I hate maintainers abusing it that way.) 15:39:35 just tell me how can I help with 4.10 testing on all affected releases 15:39:37 so, I would've greatly prefered to reach more consensus. I don't like not having all kde-sig'ers onboard and in favor of this 15:40:42 Martix: what important for testing ist update process from 4.9.5 to 4.10 15:40:58 Martix: we'll be doing f18 for sure, at least. 15:41:15 rdieter: than I'm counting with that on f18 15:41:27 the update should work without any deps issue 15:41:58 That's the minimum. 15:42:04 It should also work without any runtime issue though. :-) 15:42:22 Kevin_Kofler: yes, it's next step :) 15:43:24 So, anyone else share my reservations about having a lack of 100% consensus, or just move forward anyway? 15:44:09 if there's no objecttion i can take care of the f17 build 15:45:32 no objections, fyi, builds in f17-kde tag already include: akonadi-1.9.1-1.fc17, soprano-2.9.0-1.fc17, iris-1.0.0-0.12.20110904svn812.fc17, sip-4.14.4-1.fc17, PyQt4-4.10-1.fc17 15:45:40 rdieter: we are too weak :) 15:46:36 jreznik: maybe. it's definitely not black or white issue though. I must admit that pros do seem to outweigh any cons 15:47:28 doing it means less work, better experience for fedora users in the long run 15:49:06 So, can I log an #agreed that we're going to do this? 15:49:37 yes 15:50:03 #agreed We will be pushing 4.10.1 to Fedora 17. 15:50:16 #topic Test Day next week 15:50:28 So, anything to say about the test day? Martix? 15:50:51 I'm going to update test cases this week 15:51:26 proposed list of new test cases would be helpful 15:52:11 #action Martix is going to update test cases this week 15:52:18 #halp proposed list of new test cases would be helpful 15:52:34 which day exactly? 15:52:40 * rdieter forgets 15:52:42 14 March 15:52:58 ok, thursday, gotcha 15:53:02 #info Reminder: The Test Day is on Thursday, March 14, 2013. 15:53:21 #topic Open Discussion 15:53:24 Anything else? 15:54:46 appmenu-qt can be added somewhere to be installed by default? This feature added in 4.10 15:55:00 -1 15:55:19 Dragging this in in an update doesn't make sense. 15:55:21 nucleo: will add to comps 15:55:33 for new installations 15:55:37 rdieter: But it should stay optional in F17/F18. 15:55:38 that's what we did for f19, install by default, but allow it to be removed 15:55:50 Kevin_Kofler: right, no hard dep 15:56:09 I mean optional as opposed to default. 15:56:21 (i.e. opt-in rather than opt-out) 15:56:35 It doesn't make sense to add default components to comps in an update. 15:56:50 People installing later should not get different packages than those who installed at GA and updated. 15:56:56 oh 15:57:04 it useful for small screens as on eeepc gives some more free space 15:57:21 Kevin_Kofler: they're already getting different packages due to packaging differences anyway 15:58:03 anyone else with an opinion for or against making appmenu-qt default in f18 comps ? 15:58:24 s/differences/bugs/ then. ;-) 15:58:45 appmenu-qt can be added in 4.10.1 update for F17 15:59:00 nucleo: it's already available to be installed 15:59:08 now 15:59:21 f17-updates-candidate 15:59:24 the issue is whether @kde-desktop comps group should install it by default... or not 15:59:25 http://koji.fedoraproject.org/koji/buildinfo?buildID=397292 15:59:41 oh, oops 16:00:21 i assumed previous maintainer had done so 16:00:39 and this http://koji.fedoraproject.org/koji/buildinfo?buildID=397291 but -2 in f18-updates 16:01:10 notice it's changelog "cosmetics" , update for that is not needed 16:01:49 if -3 will be in F17 then -3 should be also in F18 16:02:14 not sure if appmenu-qt is useful for kde< 4.10, so if we do kde-4.10 then it can be added in the update group, sure 16:02:44 oh, no 2.fc17 build either? rats, ok, update needed for both then it seems 16:02:57 * rdieter has to go to another appointment 16:02:58 http://koji.fedoraproject.org/koji/packageinfo?packageID=15117 16:03:20 We're over time anyway, let's close the meeting here. 16:03:37 #endmeeting