17:06:01 #startmeeting 17:06:01 Meeting started Mon Jul 18 17:06:01 2011 UTC. The chair is bmwiedemann. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:06:01 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:06:10 As always, today's agenda is on http://en.opensuse.org/openSUSE:Testing_meeting 17:06:10 You can still add to the agenda on the wiki while the meeting is in progress 17:07:07 #topic MS3 experience 17:07:46 the final MS3 is still not out, but I upgraded one of my laptops to factory and it still worked 17:08:27 What kernel on factory? Is it 3.0? 17:08:30 openQA is still showing smaller problems (e.g. amarok segfaulting on KDE-Live) 17:08:41 3.0-rc6 right now and MS3 should have rc7 17:09:16 I still run MS2 17:10:18 should we meet next monday to talk about MS3 then? 17:11:04 Yes. 17:11:50 +1 17:12:06 OK. let's move to the next topic then 17:12:38 #info will discuss MS3 on 2011-07-25 17:12:52 #topic Request to rename MS6 to Beta 17:13:39 LWFinger: what is the state of the discussion on that topic? 17:14:20 Most people have been supportive. 17:15:09 I hope you have followed the d=iscussion on the mailing lists - postings have been on project, factory and testoing. 17:15:56 Coolo was skeptical that it would make a difference, but has agreed. He will want metrics on the value. 17:16:46 We have an offer of help for publicity. 17:17:06 That covers the highlights. 17:17:39 Any questions? 17:18:50 I had only read the summary on testing ML and proposed two crude metrics there 17:19:21 Your ideas are good, but we likely need more. 17:21:50 maybe we could have some way to count users? e.g. via the downloads that always happen after install (such as flash-player) 17:22:15 page hits? 17:22:59 can we have the number of downloads? 17:23:33 I think, coolo can get logs from download.o.o 17:24:03 for the product they publish how many downloads happend 17:24:19 while this excludes mirrors, it is still a meaningful number 17:24:29 so maybe collo can give us this number per MS 17:25:37 yes. that would be helpful. 17:25:54 The bug reports may be more significant as they reflect actual testing. 17:26:13 we can combine this 17:26:27 but they also reflect the buggyness of the software 17:27:02 Of course, but will 12.1-beta be any buggier than 11.4-MS6? 17:27:29 I already have a bugzilla report about this 17:27:40 not on MS level , but per release 17:28:36 LWFinger: yes, bugs can be added after MS5/6 (e.g. because people want to get their features in last minute) 17:29:13 The number of bugs found in GM after 6 months will be the really critical number. 17:29:50 Are we not feature frozen after MS4? 17:29:51 critical for what? 17:30:37 Critical as to the value of the name change. Did we find bugs early enough to fix them before GM? 17:31:37 I wouldn't put too much into this name change 17:31:55 maybe it makes more sense to have some statistics 17:32:28 I had two nice reports showing whats going on 17:32:53 What reports? 17:33:06 comparing releases 17:33:16 comparing reales per component 17:33:42 was interesting to see where bugs appeared most 17:34:16 Are these reports available? 17:34:45 I have to recreate them 17:35:02 bugzilla has a report.cgi to do those stats - I also linked it in my email 17:35:21 but as with every statistics I will not distribute them 17:35:27 to the public 17:37:17 the conclusion is, most bugs are found in the final 17:37:24 bmwiedemann: Thanks. I just created the table. 17:37:58 likely because final has a) most users and b) most usage time 17:40:43 yupp, so you can' heardly compare this with the milestoones 17:42:17 s/can'/can't/ 17:43:01 "can hardly compare" sounds better ;) 17:43:21 We can hope that the trend of decreasing numbers in final between 11.3 and 11.4 continues. 17:43:23 right 17:44:20 we should try to do this bug day more continously 17:45:40 I added 11.2 to the table and there were fewer bugs in 11.3 final than in 11.2. The trend is good. 17:46:13 we want to do at least one big bug-squashing party around MS6. but could do one or two smaller bug events before 17:47:36 jradzuweit: what should be the main focus? re-testing older 11.4 or 12.1-MS bugs? 17:48:25 main focus 12.1, but if you are testing in certain areas 17:48:38 why not checking if old bugs are still there 17:49:02 I think we need to do both. 17:50:12 Perhaps we could have a party after MS4 that concentrates of 11.4 bugs still in 12.1. 17:50:41 Then after Beta, check for the new ones in 12.1. 17:51:26 we could put some on a wiki page 17:51:46 and request the community for retests 17:52:54 doing a whole day testing, my wife will kill me ;) 17:53:19 jradzuweit: I would re-activate my openbugs.zq1.de tool for that occasion. it is so much faster than wiki or bugzilla 17:53:33 sure 17:57:15 #info rename of MS6 to Beta is likely 17:57:33 #topic open bugs day planning 17:59:07 MS4 is not very far away, so we would have to start planning an open bugs day soon 17:59:40 Roadmap says MS4 comes on 2011-08-11 18:00:49 Would a Sunday work? If so, perhaps 08-21. 18:01:57 that would allow for a delayed release, too 18:02:46 so would be good 18:03:27 agree, but I can't attend all the day 18:03:40 ok, I have to leave now 18:03:51 few people will be awake 24h that day ;) 18:03:56 so it is alright 18:04:08 bye 18:04:12 Ciao 18:04:24 The main thing is to attract others besides the TCT. 18:04:56 As soon as we set a date, I'll start the publicity. 18:05:19 be sure to email news@o.o 18:05:33 Yes. 18:07:26 OK. anything else to discuss? 18:09:11 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:09:32 #endmeeting