16:00:01 #startmeeting Fedora QA meeting 16:00:01 Meeting started Mon Nov 15 16:00:01 2010 UTC. The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:01 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:06 #meetingname fedora-qa 16:00:06 The meeting name has been set to 'fedora-qa' 16:00:13 #topic Gathering 16:00:16 * kparal up and running 16:00:18 * fenris02 waves 16:00:40 * thomasj lurking 16:00:46 * Viking-Ice comes charging in armed with bacon.. 16:00:49 * jskladan emerges from the shadows 16:00:49 Hi all ... *very* light agenda today http://lists.fedoraproject.org/pipermail/test/2010-November/095558.html 16:01:14 We'll be without rhe and adamw today 16:01:24 Howdy kparal fenris02 thomasj Viking-Ice jskladan :) 16:02:05 jlaska: good as always, hope you're all right too 16:02:10 okay, will get started in 30 seconds 16:02:20 * mkrizek is here 16:02:24 jskladan: doing fine ... just the right amount of coffee today :) 16:02:31 * jlaska tips hat to mkrizek 16:03:53 * jlaska looks if wwoods is in the shadows that jskladan was lurking in 16:04:08 #topic Previous meeting follow-up 16:04:18 This is a quick one ... I had no recorded action items from last week 16:04:31 I have a standing item to organize the retrospective feedback, but I'll save that for next 16:04:46 anything I missed that folks want to hilight from last week? 16:05:12 if not ... let's dive into the agenda 16:05:21 #topic F-14 QA Retrospective last call 16:05:33 I had this there last week ... fully intending to not say much more on the topic 16:05:38 but we continue to get more feedback 16:05:42 #link https://fedoraproject.org/wiki/Fedora_14_QA_Retrospective 16:06:10 As I mentioned earlier, I have an open item to organize this feedback into an actionable list of tasks open to anyone 16:06:31 For folks who remember, we followed the same process for F-13 ... so there won't be any surprises 16:06:41 so ... feel free to jot down any more ideas 16:06:51 A good one landed today from Spot regarding the autoqa 'upgradepath' test 16:07:10 and running in batch against the release milestones as we did in F-14-Final for repoclosure 16:07:19 more discussion on the wiki for that 16:07:25 ah, good idea 16:07:46 certainly only a problem while we're still in the permissive phase of the 'update criteria' tests 16:07:48 upgrade from $N-1 or $N-2 or both? 16:08:14 fenris02: iirc, kparal can correct me, but it will test from N-2 to rawhide 16:08:23 ensuring that upgradepath in 'updates' is maintained 16:08:24 whoah. neat 16:08:34 it's been running for some time now, and catching failures 16:08:44 is it reporting them anywhere? 16:08:46 but we've only been sending results to autoqa-results@lists.fedorahosted.org 16:08:54 * fenris02 nods 16:08:59 that will be changing soon ... but mkrizek can talk more about that shortly 16:09:00 upgradepath ensures all the releases are fine at once 16:09:16 anything else folks want to add on the F14 QA retrospective? 16:09:25 we've got a lot of good ideas and trouble areas on the wiki 16:09:28 plenty to build on for F-15 16:10:01 #topic QA and Docs team cooperation 16:10:16 Sparks mentioned this topic last week ... and I neglected to include it in the meeting agenda I sent to the list 16:10:19 Sparks: around? 16:10:47 if I understand, his comments were around "testing" of the official release documentation 16:11:16 I don't know much about testing documentation, other than reading it for accuracy, but perhaps I can pull in some folks who are more skilled in docs verification 16:11:50 probably means to test whats written 16:12:06 In a similar context as the qa retrospective, I'd love to learn more about what types of issues/problems surfaced that demand improved QA engagement 16:12:11 Viking-Ice: yeah, that could very well be it 16:12:44 iirc, during F-12 (or was it F-11) we had a test event around installation following the posted installation guidelines 16:12:55 where 'test event' was a request to the list iirc, I could be wrong though 16:13:26 so anyway ... Sparks & I can catch up more later. But if anyone has ideas on ways to improve this ... toss them into the QA retrospective wiki 16:13:57 kparal: I was about to jump to open discussion ... but do you want to bring up any AutoQA topics first? 16:14:32 well 16:14:42 #topic AutoQA revisited 16:14:49 I can announce the roadmap 16:15:06 we try to organize a little better and make even some future plans! 16:15:13 therefore I created https://fedoraproject.org/wiki/AutoQA_Roadmap 16:15:39 it's just a proposal for now. but interested people can have a look at it what features we plan to bring you and when 16:16:05 Oooh, I like it :-) 16:16:12 kparal: yeah, nice format 16:16:20 and that reminds me ... I need to get cracking on packaging 0.4.3 :) 16:16:40 apart from that, mkrizek is working hard on posting bodhi comments from autoqa tests 16:16:48 kparal: everything is in 'master' that you want, right? 16:17:04 jlaska: correct, I think you can create a release from the current HEAD 16:17:47 #info Draft AutoQA roadmap available at https://fedoraproject.org/wiki/AutoQA_Roadmap 16:18:05 #info mkrizek working on bodhi comment support for AutoQA tests 16:18:27 well, that's all for today I think. expect more next week, we are slowly coming into speed :) 16:19:08 I like your work 16:19:27 I've got a few thoughts I'm attempting to organize from the installer folks on how we can build some forward momentum around AutoQA and installation testing 16:20:26 I'm attempting to organize ideas on the wiki ... definitely in draft shape at this point https://fedoraproject.org/wiki/User:Jlaska/Fedora_15_Installation_automation_ideas 16:21:18 kparal: I don't know about you ... but exciting to have AutoQA back as the focus 16:21:27 these darn releases are so needy for testing :) 16:21:43 yes, I like working on it again 16:21:51 Alrighty ... I guess it's open discussion time 16:22:09 #topic Open Discussion - 16:22:20 Anything not already discussed that folks would like to bring attention to? 16:22:53 * kparal notes: don't be mistaken, we don't create AutoQA so that we can test Fedora. we release Fedora so that we can have something AutoQA can test :) 16:23:42 AutoQA is a hungry beast and it needs feeding :) 16:24:52 alright ... if no other topics ... we'll close out in 2 minutes 16:26:22 30 seconds ... 16:27:16 alright, I think we're done today 16:27:18 thanks all for your time 16:27:34 I'll follow-up with minutes to the list later today 16:27:35 #endmeeting