17:00:59 #startmeeting 17:00:59 Meeting started Mon Apr 11 17:00:59 2011 UTC. The chair is bmwiedemann. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:59 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:01:17 Hello everyone 17:01:24 As always, today's agenda is on http://en.opensuse.org/openSUSE:Testing_meeting 17:01:24 You can still add to the agenda on the wiki while the meeting is in progress 17:01:24 hi 17:01:37 Hi. 17:02:42 #topic Review Open-Bugs Day 17:03:43 Well - we were way to few people this time 17:04:41 still, quite a number of updates. 17:05:14 oh yes - and even if we got some "flak" about closing bugs as obsolete it was a good round 17:05:29 but re-testing on current versions would be good 17:06:12 I still think closing them was the right thing to do. 17:06:38 it's just one person complaining 17:06:42 because just blindly closing anything is as nearly good as ignoring all the old stuff 17:06:44 in many cases its not even possible 17:07:05 If a bug hasn't been touched since 2007 or 8, then it is not viable. 17:07:14 have anyone seen any of the bugs closed get reopend? 17:07:34 and if reopend did the bug get moved to a current target? 17:07:49 not mine. but I moved some of them to 11.4/5 17:09:39 I pushed the wrong button and may have missed something, but a few bugs were reopened. 17:09:58 I haven't seen any of mine reopend either - and from my quick scan of the bugs@os list it can't have been many 17:10:27 In my view its better to close a bug to many than letting them bitrot 17:10:54 it has potential to driver bug-reporters away 17:11:08 and miss bugs that are still in there 17:11:46 iznogood: I agree. The ones that were reopened were switched to 11.4 as they should have been. 17:12:35 Is closing an obsolete bug any worse than ignoring it? 17:12:55 ok - how about a comprimize - if the "tester" is unable to test the bug on his/her system - set the bug to needinfo -> to the original reporter - no comment in 30 days after bugday close it 17:13:13 iznogood: would be very good 17:13:44 I did run into a number of bugs where the needinfo request was two years old! 17:13:45 I recomend entomologist for everyone as a tool to follow up on bugs 17:14:01 LWFinger: in those cases - close it 17:14:06 just closing everything could be done by a script, so we would not need an Open-Bugs-Day for that 17:15:29 iznogood: I did. 17:15:34 good 17:16:47 bmwiedemann: the bugdaytool - I kinda felt it kept sending the same bugs my way - bug? :-) 17:17:23 http://tinyurl.com/392jnb - take a look here - there is still a few bugs from 10.0 and 10.1 left 17:17:55 iznogood: it is designed to be simple and to work with 100+bugs. so it does not work well when you use the new filter feature 17:17:59 I was able to close the last 4 from opensuse 10.2 yesterday, but we should make an effort to close the remaing ones 17:19:43 btw - what should we do with enhancments bugs? - I often was unsure if the bug were fixed or not 17:20:10 moving to features.o.o might be an option 17:20:24 just move the bugs in such cases, and hope that the asignee ( or list) that gets it sees if its fixed or not? 17:20:28 in fact - feature requests needs to be created out of them if they are not implemented yet 17:21:07 but the questions is if this does make sense for really old bugs 17:21:26 should we do that? - what if the requester has long gone away / dead / distrochange 17:22:03 I'd look if it seems still to be a useful feature 17:22:07 I would not do this for enhancement bugs prior to 11.3 17:23:11 IMHO missing features don't magically vanish like bugs 17:23:29 so there are plenty >2 year old good ones 17:24:03 But they still need to be kicked one way or another. 17:25:19 yep 17:26:29 With the 10.X enhancement requests, I said "If still needed, take it to openFATE". 17:26:51 if people know where to find that? 17:26:59 I would consider it much more important to push enhancement bugs of 11.3 and 11.4 to fate if they are not there or implemented yet 17:27:15 I for one don't feel like making req at openfate for other people 17:27:55 OK. having your name there as "Requester" might not be right. 17:28:15 Agreed. 17:28:18 but linking to https://features.opensuse.org/ might be good 17:28:23 indeed 17:28:25 but you should mention "...from bug report #123456" 17:29:18 Holgi: we should have a wiki page describing that procedure 17:29:48 bmwiedemann: do you think that 17:29:52 ? 17:30:13 there are 163 open enhancement bugs for 11.3+ 17:30:28 ok 17:31:54 the wiki page could describe why openFATE is better to track those, too 17:32:11 so we only need to link there 17:32:18 I agree 17:32:41 * iznogood hides from AI to create a wiki 17:34:00 shall we move to the next topic? 17:34:09 I want to mention 17:34:25 that we need to do more advertising of such an event next time 17:34:45 news.opesuse.org, opensuse-announcement@os.o etc. 17:35:01 how about sending out an ical with the mail aswell - easy import into calender 17:35:05 just the date in the calendar is not enough 17:35:06 we did for the first one - which might be why there were more people 17:35:32 iznogood: attachments are not liked. but URLs should work. 17:36:32 Saturday is bad for the Newsletter as if comes out late on that day. 17:36:39 just what I think - no bashing at all 17:37:06 it went wll from my point of view since it was for the first time 17:37:07 so better plan a Sunday next time? 17:37:13 so we learned that saturdays are out 17:37:15 I think so. 17:37:48 but even if we "start" on sunday, how about opening the bugday tool on friday already 17:38:01 sure 17:38:15 Yes. 17:39:54 Next topic? 17:40:00 the detailed roadmap for 12.1 is not yet there, so we don't know yet when the last Milestone (MS6?) will be out. 17:40:15 we will schedule that bugsquashing later then. 17:40:30 #topic Post-release analysis of 11.4 - What was Good or Bad 17:40:48 This one is mine. 17:41:27 I thought the best thing about our cycle was openQA. 17:41:36 :) 17:41:57 * iznogood had 2 whole weeks on 11.4 before returning to factory, so I can't input much here 17:42:31 You deserve much credit. The worst thing was that we still got bugs added betweem RC2 and GM. 17:42:44 I wonder how many people used factory-tested 17:43:04 apart from me 17:43:29 Ping someone from obs-chan, they might be able to pull out download stats 17:43:39 I uploaded the RC2.1 to have it better tested before GM 17:43:44 I did. On this point, 11.4 was better than 11.3 where networking was broken. The forums are still dealing with that. 17:45:03 I guess my question is "How do we get more time between the last RC and GM?" 17:45:15 if we want a (close to) bugfree release we need more testing before the last milestones 17:46:07 ie - all blocker bugs should be fixed before last milestone / or at least before rc1 17:46:17 I talked to coolo about more/longer freeze and he said that it could make people move to Factory instead of stabilizing the current release 17:47:08 and that people wanting a solid openSUSE could use the 11.3+updates which has seen 8 months of intense testing+bugfixing 17:48:20 * iznogood thinks factory has been more or less stable last year atleast 17:48:21 Of course, there are some things that cannot even be tested with milestones if you need Packman support. 17:48:42 packman has a essential repo for codecs now - that helps a lot 17:49:04 doesn't packman build for milestones? 17:49:08 iznogood: Are those release agnostic? 17:49:30 no not totally - it lags somewhat behind 17:49:43 bmwiedemann: I don't think so. 17:50:06 or one could just by gstreamercodecs from fluendo, works for me 17:52:56 but lets get back on topic 17:53:44 For me, 11.4 has been good from the start, but I never run the standard kernel. 17:54:36 I had some trouble with pulseaudio, causing trouble with skype after some minutes. disabled it manually and everything is now working 17:55:30 PA is always trouble, but my audio requirements are minimal. I also use a limited set of apps. 17:55:45 anyone here run KDE3 on 11.4/tumbleweed, or seen my opensuse-kde thread about small Konq4 menu fonts? 17:55:52 if it is used by default, it should be make working 17:56:04 a-865: no 17:56:27 No, I'm on KDE4. 17:56:42 bmwiedemann: works for me, so get bugfiling 17:57:03 * iznogood thinks PA is the next best thing since sliced bread 17:57:30 Until last night, I had no idea the opensuse repositories for 11.4 had KDE3 in them 17:57:47 iznogood: with PA mono sound comes out on the internal speaker only here :-/ 18:00:15 Holgi: do you have pavucontrol installed? ( or whatever the kde version is called) 18:01:28 iznogood: I use the (gnome?) mixer with lxde 18:01:43 iznogood: tired to set all accordingly, but not able to change 18:01:53 but I did not create a bug report as well 18:01:58 so far 18:01:58 ok - lets look into this after the meeting 18:02:15 any other opinions on 11.4 18:02:16 iznogood: it's my work station at work - I'm at home now 18:02:30 Holgi: an other time then 18:02:34 iznogood: so no way to debaug now 18:02:40 debug 18:04:02 I'll repeat : any other opinions on 11.4 18:04:23 bettern 11.3, not bettern 11.2 18:04:56 so a-865 whats broken for you out of the box? 18:05:15 ie - what did we miss as in bugs for that release? 18:05:37 bug 584493 18:05:46 same as 11.3 18:06:15 and the parallel boot thing 18:07:16 stock kernel will not cause init 0 to complete on old Piii 18:07:30 just sits there after umounting everything 18:08:03 and it work with non-parallel boot? 18:08:20 yup 18:08:48 Can that be changed from the GRUP options line? 18:08:58 s/GRUP/GRUB/ 18:09:06 bug 683476 18:09:14 I don't think so 18:09:44 bug 675793 18:10:04 oops, I meant bug 675370 18:10:30 bug 674919 18:11:21 parallel boot here bug 665720 18:12:33 KMS is certainly a problem. For me, the one machine that uses i915 is OK, but all my nVidia cards are broken in 2.6.37 - some fixed in 2.6.38. 18:13:22 KMS is why I refuse to suggest 11.3 to anyone 18:13:24 someone reported graphics problems with a Lenovo notebook 18:13:56 was much too green at release time 18:14:05 green=immature 18:14:15 "nomodeset" is not that hard to put in the GRUB line. 18:14:50 Those devs have a really tough job. 18:14:56 nomodeset disables intel driver 18:15:27 unless maybe it shifts to intellegacy driver 18:15:29 Yes - it reverts to the framebuffer driver - just like 11.2. 18:15:50 framebuffer limited to 1024x768, right? 18:16:07 so nomodeset is no option here 18:16:29 No. I'm using the nv version at 1280x800 - the native res for my screen. 18:16:40 665720 had been duped, but werner reopened it 18:16:49 now I have to figure out how to respond 18:16:54 big time consumer 18:20:44 that reminds me: anyone else having problems to play an .ogv in firefox4? it seems to only fail on one of my machines. 18:22:19 bmwiedemann: link to test? 18:22:21 I just tested on openQA. Worked fine. 18:22:45 iznogood: http://openqa.opensuse.org/ has one on the lower part 18:24:47 bmwiedemann: works here 18:25:07 OK. then my install is somehow borked 18:25:42 btw - yast says your password is to simple for the testmaschine 18:26:08 yep. it is "nots3cr3t" 18:26:57 but does not really matter as KVM there runs in NAT mode - not reachable from outside 18:27:47 That one doesn't look that simple to me. It must be that all the letters are lower case. 18:28:44 it is also that it contains a dictionary word 18:30:12 But the topic at hand - a-865 had some bugs that did not get fixed in time, but there is an assingned person looking into the bugs atleast. - Do we have more to discuss, or should we call it quits for this one? 18:30:58 we need to schedule next meeting 18:31:23 + one month - isn't that good enoght? 18:32:14 Certainly no sooner than that. 18:32:45 If we have milestone 1 we should have one right after ? 18:33:04 Yes. 18:33:24 2011-05-09 might work then? 18:34:09 OK. 18:34:13 Sure - Is the timeslot ok for everyone? - ie noone that needs to get up in the middle of the night to attend? 18:34:15 roughly two months after 11.4 18:34:47 It starts at noon for me. 18:35:13 so 17:00 UTC again 18:35:24 great - voted 18:36:03 #topic next meeting 18:36:16 #agreed next meeting will be 2011-05-09 17:00 UTC 18:37:13 any more topics to discuss? 18:37:25 None here. 18:37:38 nope 18:38:09 Then I will close today's meeting. Thanks everyone for attending. I will add links to the logs on http://en.opensuse.org/openSUSE:Testing_meeting 18:38:14 #endmeeting