15:02:10 #startmeeting Fedora QA meeting 15:02:10 Meeting started Mon Jul 26 15:02:10 2010 UTC. The chair is kparal. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:10 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:24 #topic Gathering interested mass 15:02:35 * j_dulaney is here 15:02:35 let's see if there's anyone interested in the meeting today 15:02:43 several people are not able to attend 15:02:49 * dafrito is here 15:02:51 * tertl3 arrives 15:03:05 * Viking-Ice half in half out.. 15:03:10 morning 15:03:33 * kparal tips hat to everyone 15:03:46 * fenris02 waves 15:03:48 wwoods may be lurking? 15:03:55 he does that 15:04:07 lurking, or lairing? 15:04:46 hah, I would really like to know what it means in english, but literal translation to czech is really funny 15:05:38 alright, seems we all now 15:05:45 go with that then =) 15:06:08 jlaska is not available today, so I'll try to (hardly) replace him 15:06:21 jskladan is also out, so is vaschenb 15:06:47 #topic Previous meeting followup 15:06:57 do we have any issues to check from the last time? 15:07:03 * kparal searching 15:07:16 we usually do 15:07:18 The proventester followup thingy? 15:07:32 last time: http://fedoraproject.org/wiki/QA/Meetings/20100719 15:07:35 Can't remember who was supposed to do that, or even if it was supposed to be done. 15:07:52 only one action item: 15:07:53 "maxamillion to set up a weekly outstanding proventester mentor request checkin" 15:08:05 That's what it was 15:08:10 looks like he's awol today =) 15:08:18 eheh 15:08:30 alright, we will skip that point 15:08:52 so let's go to the new topics 15:08:57 jlaska proposed: 15:09:00 #topic F14 Alpha test milestones 15:09:17 #link http://poelstra.fedorapeople.org/schedules/f-14/f-14-quality-tasks.html 15:09:28 the important items: 15:09:33 > Thu 29-Jul  Wed 04-Aug  Test Alpha 'Test Compose'Fri 30-Jul  Fri 30-Jul  Alpha Blocker Meeting (f14alpha) #3 15:09:43 * kparal tries again 15:09:46 Thu 29-Jul  Wed 04-Aug  Test Alpha 'Test Compose' 15:09:46 Fri 30-Jul  Fri 30-Jul  Alpha Blocker Meeting (f14alpha) #3 15:10:22 so it should be only three days and we can have our hands on first official F14 bit 15:10:29 yup 15:10:30 Nice 15:10:47 systemd went default in rawhide yesterday, so that should be in 15:10:54 adamw: anything you want to add to this topic? it's your floor more than mine :) 15:10:57 Nice 15:11:51 alright, it will be quick today :) 15:11:51 Oxf13: if you're around, might it be a good idea to do a test-test-compose to see if you can build working images at all with systemd? just so you don't hit problems on wed/thur and get delayed 15:12:15 can you boot with selinux enabled now? (do you get a graphical greeter yet?) 15:12:39 theoretically i think both of those are meant to be fixed 15:12:53 i haven't actually tested yet since the switch was broken (lennart muffed the dependencies) 15:12:55 adamw, afaict, they are still broken. 15:13:41 fenris02: http://koji.fedoraproject.org/koji/buildinfo?buildID=186032 is supposed to help the selinux stuff 15:13:43 There went few selinux patches from Dan into systemd 4 15:13:52 anyhow, i'll try and test it later 15:14:21 alrighty, thanks. let's go into next topic 15:14:26 I'll try to give it a manual test on some of my hardware 15:14:35 #topic AutoQA update 15:14:43 yup, we should try and test it out if we can. 15:15:03 seems that I'm the only one for AutoQA update today 15:15:08 well then 15:15:30 I committed vaschenb's 'helloworld' patch 15:15:45 and broken a lot of stuff :) 15:15:57 aha! progress! 15:16:16 so the fixes are continuously flowing and repairing and breaking new stuff 15:17:04 I also prepared a big 'control.autoqa' branch that contains patchset for 1. multihook tests, 2. better test scheduling, 3. autotest labels support 15:17:18 * j_dulaney is still trying to figure out AutoQA so he can help 15:17:21 we are really waiting for wwoods' expertise to review this patch 15:17:54 but that's stuff that's vital for the package update test plan right? 15:17:55 but it should be merged to master hopefully soon and then we can do some really wild stuff, haha 15:18:00 adamw: yes 15:18:07 cool. 15:18:50 the AutoQA infrastructure now undergoes big rewrites, so maybe it will be better to wait a little while, j_dulaney 15:19:05 under to documentation is corrected and so on 15:19:12 s/under/untill 15:19:20 kparal: I've noticed on the mailing list 15:20:05 I have heard that wwoods' hardware had mailfunctioned, so it may take a few days until he's up and running again and accepting patches 15:20:09 alright, that should be it 15:20:27 #topic Open Floor - your issue here 15:20:38 what do you want to discuss? 15:20:45 live lite music spin coming soon 15:20:58 (your_ad_here)! 15:21:20 ccrma kernel possible for music spin? 15:21:40 no point, and it would break a great many items 15:21:42 * kparal has no idea what ccrma kernel is 15:21:43 um, let's see. no news on proven testers, really. we're looking very light on test days for this cycle, so if anyone has any ideas, please pitch in. 15:22:08 #info Please provide ideas for Test Days 15:22:25 ie, things to test? 15:22:45 j_dulaney: basically a new or some old feature that needs to be tested 15:22:45 anything from an idea for a test day through to 'hey, i want to organize one' 15:22:50 can I ask a question? 15:22:56 tertl3: sure, go on 15:23:31 are the mesa-experimental going to going to still be 'experimental' in 14? 15:23:35 kparal: roger 15:23:49 adamw: How would I organize a test day? 15:23:57 j_dulaney: https://fedoraproject.org/wiki/QA/SOP_Test_Day_management 15:24:05 (boy, i love having an easy answer for that :>) 15:24:06 j_dulaney: https://fedoraproject.org/wiki/QA/Test_Days 15:24:17 adamw: do you know about mesa-experimental? 15:24:24 adamw: kparal: thanks 15:24:39 tertl3: it depends. what happens is that the package exists if there are any drivers still considered 'experimental' by the mesa folks. if there aren't, it doesn't. the content changes - for e.g., the r500 driver used to be in there. 15:24:47 tertl3, look at rawhide? 15:25:14 adamw, fenris02 thnks :) 15:25:26 tertl3: nouveau may not be 'experimental' for f14 final, if we wind up shipping gnome-shell by default, as you'd want it installed by default. but that's just me speculating. ben skeggs (darktama) would know best. 15:25:44 alright, any other topic? 15:26:23 adamw: I don't like the sound of that 15:26:37 I've had trouble with nouveau 15:26:43 kparal: let's see, i had one thing...just a sec 15:26:59 kparal: oh yeah, 'polish' release criteria 15:27:09 but may be best to leave for next week since jlaska's interested in that 15:27:09 i hear nouveau has problems with blender 15:27:09 #topic Polish release criteria 15:27:16 ah 15:27:24 alright 15:27:28 we're both fairly sure we were going to add a release criterion or two for 'polish' issues 15:27:35 artwork stuff 15:27:56 Also, something I've had trouble with in Rawhide 15:27:58 but we couldn't find any of the prior discussion of it, so we'll probably just start over, and we should propose one or two criteria to add to the final release. 15:28:19 adamw: Is not that usually something that the design team makes sure is a ok? 15:28:35 #info adamw and jlaska will propose one or two criteria about artwork stuff to add to the final release 15:29:03 Viking-Ice: sure, but that doesn't mean it doesn't go in the release criteria 15:29:08 Viking-Ice: software is also usually taken care of at devel team and still we have it in release criteria :) 15:29:18 kparal: exactly what I was gonna say :) 15:29:36 ok 15:29:50 #topic Open Floor 15:30:13 I noone else has some topic, I think we've broken record in the fastest QA meeting ever :) 15:30:14 I have a little bit of a follow up 15:30:27 j_dulaney: go ahead 15:30:53 Namely, the instructer at CCC said that he would get his OS class to do some testing for us 15:31:08 That's it for now, fall semester's still a few weeks away 15:31:09 #topic School class testing 15:31:20 ah, no more details? 15:31:30 j_dulaney: cool, i'd been wondering about that. 15:31:55 we are surely looking forward for any support 15:32:05 kparal: I believe that he's going to have everyone in the class sign up for proventesters, but I could be mistaken on that count. 15:32:07 I just wonder if we have enough simple tasks for 30 students :) 15:32:21 proventesters sounds like a good idea 15:32:31 If we dont we can always make up couple of things ;) 15:32:38 #info the class could try proventesters tasks 15:32:47 kparal: probably more like six or seven, ten at the most 15:33:11 that's fine. I think it's even better than 30 15:33:41 ok, thanks for info j_dulaney 15:33:47 roger 15:33:52 #topic Open Floor 15:35:18 ok, thanks everyone for attending 15:35:24 have a great monday :) 15:35:33 #endmeeting