15:00:01 #startmeeting Fedora QA Meeting 15:00:01 Meeting started Mon May 23 15:00:01 2011 UTC. The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:01 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:05 #meetingname fedora-qa 15:00:05 The meeting name has been set to 'fedora-qa' 15:00:09 #topic Roll Call... 15:00:21 brunowolff: noted he has a conflict with the timeslot today, and will review the minutes later on 15:00:39 * tflink is present 15:00:40 adamw is on holiday today - We wish him a Happy Victoria Day 15:00:54 * kparal is not on holiday 15:01:04 heh ... a QA meeting is like a holiday, right? :) 15:01:10 :) 15:01:11 * vhumpa has just arrived 15:01:11 tflink: kparal: hello gents 15:01:19 * j_dulaney is here 15:01:19 * jlaska tips hat to vhumpa 15:01:23 * elad661 is here 15:01:29 howdy j_dulaney and elad661 15:01:35 jlaska 15:02:06 * jlaska waits another minute or so ... 15:02:24 * j_dulaney puts on some Jefferson Airplane 15:02:46 hmm who else am I missing ... 15:02:54 Viking-Ice? 15:03:08 I think jskladan is just doing some school exam 15:03:17 yes, Joza! 15:03:33 kparal: thanks, ugh, exams ... poor guy 15:03:39 okay, let's get moving ... 15:03:48 #topic Previous Meeting Follow-up 15:03:56 This is pretty easy ... since I have no action items from last week 15:04:08 anything I failed to capture that folks wanted to update the team on? 15:04:22 Armadillos? 15:04:43 * j_dulaney should be ignored 15:04:56 alright then ... let's dive in 15:05:06 the agenda is intentionally light today ... 15:05:19 so feel free to raise anything during open-discussion 15:05:31 #topic F-15 release preparations 15:06:02 #info As you no doubt have heard, F-15-RC3 was declared the winner - http://meetbot.fedoraproject.org/fedora-meeting/2011-05-17/fedora_15_go_or_no_go_meeting.2011-05-17-21.00.html 15:06:14 and will be released tomorrow as Fedora 15 15:06:20 15:06:27 * kparal cheers 15:06:28 * j_dulaney cheers 15:06:40 * j_dulaney is being stared at by the folks around him 15:06:45 these releases just keep coming :) 15:07:23 I think of that as a good thing. If they stopped, I'd be worried 15:07:24 on to the next which is right around the corner 15:07:24 but seriously, kudos to all involved in testing, bug filing or active discussion on the test@lists.fp.org 15:07:38 Southern_Gentlem: heh ... yeah, our most important release yet! :D 15:07:49 before we move on ... please gaze at the hotdog -- https://fedoraproject.org/wiki/Current_Release_Blockers 15:08:03 With mustard! 15:08:32 * j_dulaney is reminded of something he needs to bring up for open discussion 15:08:43 just NTHs left as it should be 15:08:44 so with Fedora 15 going live tomorrow ... the only outstanding items needed from us are staying on top of common issues 15:08:48 vhumpa: you got it! 15:08:52 #link https://fedoraproject.org/wiki/Common_F15_bugs 15:09:08 as usual, adamw already started documenting some of the issues tagged for CommonBugs 15:09:21 I'll do a quick sweep after the meeting to document some installer and upgrade issues 15:09:58 Anyone can get involved if they want to help, or to document a known issue close to them ... the procedure is documented on the common bug page 15:10:20 maxamillion 15:10:31 #info Document remaining 'known issues' - https://fedoraproject.org/wiki/Common_F15_bugs 15:10:41 j_dulaney: hi hi :) 15:10:44 lastly ... as Southern_Gentlem hinted ... 15:10:47 * maxamillion is late but here-ish 15:10:55 maxamillion: fashionably late! 15:10:56 :) 15:11:11 Please start thinking about what you'd like to do for Fedora 16 15:11:26 jlaska: other than take over the world? 15:11:30 #info Make notes/ideas/requests on the F15 retrospective page - https://fedoraproject.org/wiki/Fedora_15_QA_Retrospective 15:11:35 maxamillion: that's always the goal :) 15:11:45 lol 15:11:53 Target: The World 15:11:59 we have a good list of items to address for F16 already, but it's always nice to have more input 15:12:19 As usual, the F15 retrospective will become F16 fedora-qa TRAC tickets to work on 15:12:35 semi-random question, but does anyone have the sha256 checksum of the F15 desktop live release x86_64 image? 15:12:49 Anyone is welcome to work on topics already raised on the wiki, or contribute new ideas 15:13:41 maxamillion: e4007d98d9338419d79fab5d5deb9fcd477117a604d37f89f622141f3d0fa60e 15:13:47 thanks kparal 15:13:49 kparal: awesome! you 15:13:58 kparal: awesome! you're a saint and a scholar* 15:14:00 Any other thoughts on F15 before we move on? 15:14:02 haha 15:14:16 I think it went better than F14 15:14:25 jlaska: it kicks hind parts on my laptop at the house :) .... some troubles with my older gear but over all I call it a net good 15:14:29 It always seems the odd number releases go smoother 15:14:29 congrats to tflink and vhumpa for surviving their first releases 15:14:48 LOL 15:14:49 maxamillion: yeah, I know you've been finding issues recently :( 15:15:00 There is still a day and you never now crossing streets ... :) 15:15:21 vhumpa: true ... pre-congrats :) 15:15:22 vhumpa: don't say that, now I'm going to be paranoid for the rest of the day 15:15:38 * tflink hides under his desk 15:15:42 I had some trouble with F15 lately when I installed it on a server, one of those was due to a bug in comps which I already fixed :) 15:15:45 well ... I can guarruntee bugs will come that we didn't find 15:16:00 * j_dulaney goes looking for bugs with flyswatter in hand 15:16:01 let's do our best to understand the failures ... and document what we think could be done differently on the retrospective 15:16:17 elad661: a dep/conflict issue? 15:16:26 jlaska: missing firmware 15:16:30 elad661: oh oh, gotcha 15:17:12 other than that f15 was the smoothest release yet 15:17:25 elad661: if you have wood nearby, please knock it 15:17:26 :) 15:17:30 * j_dulaney still has nouveau issues, but better than F14 15:17:30 jlaska: I don't necessarily know that I found any "failures" in terms of QA ... I just think I ran into issues with hardware that's older and likely wasn't used in other testings .... and I joined the testing efforts a little late because the semester just ended a couple weeks ago 15:17:51 yeah, I think all in all it will be a solid release 15:18:00 maxamillion: yeah, that makes sense 15:18:06 * j_dulaney also joined in late due to family issues and tornados 15:18:20 alright ... so let's move on and give the AutoQA rock stars some time ... 15:18:24 #topic AutoQA Update 15:18:33 who wants to start it off ... kparal? 15:18:43 yep 15:18:54 I don't really have much, it will be quicker than ever 15:19:10 for the full week we worked on those plaintext pretty logs that we promised 15:19:21 currently it looks like this: 15:19:25 #link http://fpaste.org/sExW/ 15:19:29 #link http://fpaste.org/I7O0/ 15:19:39 * jlaska clicks 15:19:41 wow! awesome! 15:19:58 cool, an update example with multiple builds 15:19:59 the code is in origin/pretty branch and I hope it will be ready and merged into master this week 15:20:06 kparal: Nice to see there it merged well 15:20:16 * j_dulaney likes 15:20:32 it makes AutoQA much more readable 15:20:52 especially more user-friendly 15:21:01 and that's basically all updates I had 15:21:04 Are more test result going to go into the pretty log? 15:21:31 j_dulaney: all tests should have pretty logs. currently that means depcheck and upgradepath 15:21:36 I'm wondering if any fails should show up there, but otherwise maybe don't include all the passes? 15:21:47 kparal: Ah 15:21:56 j_dulaney: for future it has also been designed so that any test could use it 15:22:06 Indeed 15:22:18 j_dulaney: we're planning to keep all the passes in the logs - email reduction is a separate task 15:22:25 j_dulaney: yes, failures will be there as well, see the second link 15:22:35 Right 15:22:35 j_dulaney: I assume that's what you were talking about 15:22:53 tflink: Indeed 15:23:03 #info Worked on thoe AutoQA plaintext pretty logs (see example links) 15:24:29 I'm sure one of you is already thinking about this ... but I gather we should follow-up to devel@ with the release announcment 15:24:40 s/one/all/ 15:24:58 now you mean... AutoQA release or Fedora release? 15:25:26 AutoQA 15:26:03 when the release is ready I'll definitely write up some announcement and post it everywhere :) 15:26:23 heh, yeah I figured ... that seems to have become part of the unofficial release process 15:26:45 we'll re-evaluate release next week - keeping with our 2 week evaluation schedule 15:26:58 anything else to highlight for AutoQA? 15:27:07 not from me 15:27:13 #info Plan to re-evaluate release next week - keeping with our 2 week evaluation schedule 15:27:22 looks like that is when 0.5.0 could be hitting the shelves 15:27:48 looks like jskladan has been doing some documentation for resultsdb ... I suspect he'll have some updates on that next week (or later) 15:28:05 I have the first pass at the spam-reduction code almost done. I'm hoping to push and get comments later today now that my internet connection has stopped disconnecting every 45-60 minutes 15:28:25 * j_dulaney would like to look at that. 15:28:36 The code, not the internet issues 15:28:42 j_dulaney: jskladan today posted https://fedoraproject.org/wiki/ResultsDB_Overview 15:28:52 I didn't have time to look at that yet 15:28:57 * tflink was hoping you were offering to look at the wiring :( 15:28:58 kparal: Right 15:28:59 #info First-pass at spam-reduction code almost complete, tflink hoping to push and open for comments later today 15:29:09 #info jskladan today posted https://fedoraproject.org/wiki/ResultsDB_Overview 15:29:36 tflink: I might could if I was there (I have my electrician's license in NC) 15:30:23 * vhumpa appologizes that he will be little busy with state exam studies following 4 weeks - but will definitely stay in the loop and work on autoqa as much as he can afford 15:30:30 So it sounds like this will be another busy AutoQA week ... heads down, cranking out content for the upcoming release 15:31:06 something like that 15:31:41 I have an update on the staging server hardware ... the RHT networking request has been completed. Smooge gave an early estimate for ~ early June to have the hardware re-racked and online in the new network 15:31:59 Of course ... I'll provide an update if I hear anything else 15:32:29 nice 15:32:31 #info ETA for autoqa hardware changes (staging and production server relocation) - ~ early June 2011 15:32:36 * tflink is looking forward to having a real staging environment 15:32:56 I'm looking forward to more disk space in our production instance! :D 15:33:10 yeah, that would be better than staging 15:33:25 so ... stay tuned 15:33:33 okay, I guess we can move on 15:33:35 * j_dulaney wonders if HD donations are accepted 15:33:39 thanks kparal, tflink and vhumpa for the updates 15:33:54 you're welcome 15:33:55 I have a box full of blank 500 GB SATA drives 15:34:24 j_dulaney: hmm, I don't know how that would work with the existing space in the lab ... I (or you) can talk to smooge about that 15:34:33 Righteo 15:34:35 #topic Upcoming QA events 15:34:36 j_dulaney: nice one :) 15:34:49 kind of a moot point ... but this will be the last time for this topic in F15 15:34:50 From a former employer when he passes away 15:34:53 #info Tuesday, May 24 - Final (GA) release 15:35:03 #topic Open Discussion - 15:35:15 i/passes/passed 15:35:19 okay ... what haven't we discussed that folks would like bring up for discussion in this meeting 15:35:24 Sugar 15:35:36 yeah, have there been any updates on the NM situation? 15:35:42 Specifically, Sugar NM 0.9 15:35:44 the NM Sugar situation? 15:35:58 I've sent a patch to pbrobinson 15:35:59 #topic Fedora 15 - Sugar and NM-0.9 15:36:14 #info j_dulaney + tflink asked if there were any updates on the Sugar status for F15 15:36:22 I don't know ... I haven't been closely following the issue 15:36:30 It took a while because I knew nothing about sugar 15:36:41 But, I got a working kluge going. 15:36:44 I know adamw was in touch with probinson, but I don't have the latest 15:36:58 anyone have the bz handy on this? 15:37:06 * j_dulaney does 15:37:30 It works on my machine; hopefully pbrobinson will push my patch shortly 15:37:38 Testing would be welcome 15:37:49 j_dulaney: I'd be interested in testing that out 15:38:00 .bug 697649 15:38:01 tflink: Bug 697649 Sugar Wireless Networking broken by NetworkManager 0.9 API - https://bugzilla.redhat.com/show_bug.cgi?id=697649 15:38:06 j_dulaney: YAY! I look forward to it, will be heading home in an hour or so and will test it there 15:38:13 tflink: thanks 15:38:37 tflink: email me and I'll email you the code directly 15:38:45 might want to post the patch for review into the bug also 15:38:52 Right 15:38:58 I'll do that post-meeting 15:39:03 and get in touch with peter directly (irc or email) 15:39:08 j_dulaney: is your FAS account the same as your IRC nick? 15:39:10 to see what he needs to move forward with a build 15:39:14 j_dulaney: I'll do a scratch build of the rpm so people can tetst 15:39:14 jdulaney 15:39:17 test even 15:39:25 #info j_dulaney has a tested patch and will post to bz for review 15:39:32 pbrobinson: hey there 15:39:33 tflink: minus underscore 15:40:03 pbrobinson: anything else you want to note on this issue ... anything you are waiting for to proceed? 15:40:22 pbrobinson: will you be the one kicking off any builds once we have a tested working patch? 15:40:37 or will Simon Schampijer be handling that 15:40:48 jlaksa: I will be 15:41:06 pbrobinson: okay 15:41:31 getting a little ahead of myself here ... but assuming we have builds that work, what's the next step ... request updated .iso from rel-eng? 15:41:50 #link https://bugzilla.redhat.com/show_bug.cgi?id=697649 15:42:11 jlaska: Once I've tested the patch I'll also generate a live image using it for testing to make sure I have everything else working, from there we should be good to go 15:42:24 pbrobinson: eggsellent :) 15:42:32 * jlaska twiddles fingers in a Burnsian manner 15:42:48 :-P 15:43:02 j_dulaney: tflink: pbrobinson: anything else you wanted to highlight on this topic? 15:43:28 * pbrobinson can't think of anything of the top of his somewhat frazzled head 15:43:35 Nothing from me, other than that the patch should be attached to the bug by this evening 15:43:49 pbrobinson: let me know if there is anything you want help with 15:44:03 #topic Open Discussion - 15:44:15 alright ... anything else to cover today? 15:44:40 okay ... last call for topics 15:44:52 * jlaska sets the fuse for 1 minute until #endmeeting 15:45:00 tflink: will do 15:45:25 * j_dulaney runs off to the head. Been holding it too long. 15:45:32 tmi :) 15:45:44 okay, 15 seconds ... 15:45:53 I'll follow-up to the list with minutes 15:46:03 as always, thanks everyone for your time 15:46:09 #endmeeting