From Fedora Project Wiki

< QA‎ | Meetings

Revision as of 09:03, 18 September 2016 by Jibecfed (talk | contribs) (internal link cleaning)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


People present (lines said)

  1. jlaska (65)
  2. kparal (13)
  3. fenris02 (5)
  4. thomasj (2)
  5. jskladan (2)
  6. Viking-Ice (2)
  7. mkrizek (1)
  8. jsmith (1)

Unable to attend:

  1. Rhe (hopefully sleeping)
  2. Newgle1 (hopefully sleeping)
  3. Adamw (on PTO)
  4. wwoods


Previous meeting follow-up

  • None

F-14 QA Retrospective -- last call

Really good list of improvement areas generated so far, but more feedback never hurts.
While suggestions keep coming, this really is the Last call for feedback on Fedora_14_QA_Retrospective
Next steps ...
Organize feedback into recommendations for F-15

QA and Docs team cooperation

Sparks started thinking about ways to increase cooperation between the docs team and QA.

Started thinking about ways to increase cooperation between the docs team and QA.
Next steps ...
Identify some problems/issues that could have been caught with increased cooperation
Propose suggestions for addressing concerns identified

AutoQA revisited

Team getting back into AutoQA after F-14 release
Draft AutoQA roadmap available at AutoQA_Roadmap
Next steps ...
Draft AutoQA roadmap available at AutoQA_Roadmap
mkrizek working on bodhi comment support for AutoQA tests

Open discussion - <Your topic here>

  • No topics suggested

Action items

  • None

IRC Transcript

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

Generated by 2.7 by Marius Gedminas - find it at!