From Fedora Project Wiki

< QA‎ | Meetings


People present (lines said):

  • jlaska (91)
  • kparal (37)
  • jeff_hann (9)
  • damNageHack (8)
  • zodbot (4)
  • jskladan (3)
  • lmacken (3)
  • Viking-Ice (1)



Previous meeting follow-up

  • jlaska + fenris02 to review whether F-13-Beta is an option for
    • Already completed by the infrastructure team, yay infrastructure!

See agenda below for additional follow-up items included in specific topics

Fedora 13 RC test status

Upcoming test milestones:

  • 2010-04-16 - Pre-RC Branched Acceptance Test Plan -- DELAYED, now INPROGRESS
  • 2010-04-23 - Final Blocker Meeting (f13blocker) #2 (recap)
  • 2010-04-29 - Test 'Final' Test Compose
  • 2010-04-30 - Final Blocker Meeting (f13blocker) #3
  • 2010-05-05 - Final Blocker Meeting (f13blocker) #4
  • 2010-05-06 - Test 'Final' RC

Upcoming test days:

Recent test changes:

  • Adding i18n support to installation test plan (see details ticket#63)
Fedora 13 QA Retrospective
Ideas have already been coming in since F-13-Alpha. It's not too early to note QA issues you felt where handled well, or could have been improved. Your ideas will be used during F-14 QA goal planning. Voice your comments at Fedora_13_QA_Retrospective.

Proventesters check-in

Package Acceptance Test Plan check-in

AutoQA check-in

There has been a lot of AutoQA activities in recent weeks, jlaska asked the group to walk through some highlights.

  • Kparal provided some updates from jskladan on the results database efforts..
    • First draft of implementing the resultsdb API
    • Test suite for resultsdb API created

Open discussion - <Your topic here>

Upcoming QA events

Action items

  1. current members of the 'qa' group ... apply to 'proventesters'
  2. jlaska to follow-up w/ maxamillion after meeting

IRC Transcript

jlaska #startmeeting Fedora QA Meeting 15:00
zodbot Meeting started Mon Apr 26 15:00:08 2010 UTC. The chair is jlaska. Information about MeetBot at 15:00
zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00
jlaska #meetingname fedora-qa 15:00
zodbot The meeting name has been set to 'fedora-qa' 15:00
jlaska #topic Gathering critical mass ... 15:00
* jeff_hann is here 15:00
* kparal jumps straight into meeting 15:00
jlaska jeff_hann: kparal: howdy 15:00
jeff_hann howdee 15:00
* jskladan watching from the shadows 15:00
* jlaska tips hat towards jskladan 15:01
damNageHack hi 15:02
jlaska damNageHack: hello :) 15:02
jlaska wwoods: adamw: you guys around? 15:02
jlaska I don't think this time slot works great for maxamillion, but lemme check ... 15:03
jlaska I've got a conflict @ the half hour increment ... so let's get started 15:04
jlaska if we run over, I may need help closing out the proposed agenda items 15:04
jlaska Proposed agenda - 15:05
jlaska #topic Previous meeting follow-up 15:05
jlaska #info jlaska + fenris02 to review whether F-13-Beta is an option for 15:05
jlaska This was easy, thanks to the infrastructure team ... should already have links to Fedora 13 beta 15:05
jlaska #info Completed by the infrastructure team, yay infrastructure! 15:06
jlaska #info adamw + jlaska - Bodhi QA workflow status check-in 15:06
kparal jlaska: is it necessary to re-download the images? 15:06
jlaska kparal: good question ... I tested by downloading the images 15:07
jlaska so I don't know if the configs are pulled from the server, or are on the media 15:07
kparal ok 15:08
* kparal will test some day 15:08
jlaska kparal: that'll likely need a follow-up to #fedora-admin for guidance, I'm not sure 15:08
jlaska adamw and I spoke w/ lmacken last week, he is working to organize a lot of TRAC tickets into a bodhi-2.0 milestone 15:09
jlaska and expected to have that finished out in the next few weeks 15:09
jlaska bodhi-2.0 milestone - 15:09
jlaska Some initial requirements gathering will also take place in the coming weeks 15:09
jlaska my understanding is this will be helpful for us so we can coordinate AutoQA dependencies and document/educate 'proventesters' on the QA workflow through bodhi 15:10
jlaska we had several other follow-up items, but I've moved those into specific topics below ... 15:10
jlaska so I'll dive in, unless anyone has other thoughts 15:11
* Viking-Ice sneaks in a bit late.. 15:11
jlaska Viking-Ice: welcome! 15:11
jlaska #topic Fedora 13 RC test status 15:11
jlaska #info the current deliverable I'm working on is the Pre-RC Branched Acceptance Test Run 15:12
jlaska a new anaconda was built, and given proper karma in bodhi to be available for Branched testing 15:12
jlaska it's an unusual worflow to run through an acceptanc test, but that's hopefully something we can work out post F-13 15:13
jlaska the Friday Branched compose failed to build due to deps, but it looks like things are okay today 15:13
jlaska I'll be posting a test summary to the list later this afternoon 15:13
jlaska #info there was a F13Blocker review last week - see 15:14
jlaska We can expect the following milestones this week ... 15:14
jlaska #info 2010-04-29 - Test 'Final' Test Compose 15:14
jlaska #info 2010-04-29 - PreUpgrade test day - Test_Day:2010-04-29_Preupgrade 15:14
jlaska #info 2010-04-30 - Final Blocker Meeting (f13blocker) #3 15:15
jlaska In other F-13 testing news, there have been some i18n test considerations under discussion 15:15
jlaska you may have see this already from a ticket mail to test@ 15:15
damNageHack how is a release critical bug marked in bugzilla? 15:16
jlaska damNageHack: to mark a bug as a release blocker, you add the blocks: F13Blocker 15:16
jlaska damNageHack: and add a quick statement indicating what release criteria are impacted by the bug 15:16
damNageHack k thx. i will not do such a thing. only for my information :) 15:16
jlaska damNageHack: no worries, folks are encouraged to escalate issues of concern 15:17
jlaska we've documented what are considered the most common release criteria at Fedora_13_Final_Release_Criteria 15:17
damNageHack i am thinking of the bug with gtk2 v2.19/2.20 + thunar/pcmanfm 15:17
kparal damNageHack: current blocker list is here: 15:17
jlaska however, there are always cases where bugs don't fit a criteria ... feel free to raise those issues on the mailing list, or #fedora-qa 15:18
damNageHack k tx 15:18
jlaska So lastly, if anyone wants to contribute to additional i18n tests ... feel free to add your thoughts to 15:18
damNageHack i can see a lot of still open bugs :) 15:18
jlaska damNageHack: 18 non-MODIFIED bugs ... we have a lot of testing MODIFIED and ON_QA bugs to do 15:19
jlaska okay ... next agenda item ... 15:19
damNageHack i am sure, it can be done 15:19
damNageHack fedora has a high quality, i like that :) 15:20
jlaska damNageHack: glad to hear, we only get that because people contribute time to make it better ... so thank you! :) 15:20
jlaska #topic Proventesters check-in 15:20
jlaska We had 2 action items to follow-up on from last week 15:20
jlaska looks like maxamillion completed both of them 15:20
jlaska #info maxamillion - sent Proventester draft to for final review (see 15:21
jlaska #info maxamillion requested creation of proventester FAS group (see 15:21
jlaska thanks maxamillion! :) 15:21
jlaska he's not around right now, but I was going to ask the obvious ... 15:22
jlaska what's next? 15:22
kparal now to populate the group 15:22
jlaska yeah, is it time to request applications to the group? 15:22
jlaska do we know how to evaluate and mentor applicants? 15:22
jlaska Has bodhi been changed to use 'proventester' FAS group, instead of 'qa' for critpath updates? 15:23
kparal the mentoring process could be described, yes 15:23
lmacken jlaska: I have myself CC'd to the proventesters infrastructure ticket, but it's still not completed, from what I can tell 15:23
lmacken once it's done, changing it in bodhi will be trivial 15:24
jeff_hann jlaska: what are the qualities required for someone to become a proventester? 15:24
jlaska lmacken: is this the ticket to create the group, or to change bodhi to use proventester group? 15:24
lmacken jlaska: to create the group... once it's created, I'll change it in bodhi 15:24
jlaska lmacken: eggsellent, thank you! 15:25
jlaska #action current members of the 'qa' group ... apply to 'proventesters' 15:25
* jskladan needs to leave now. see you around, gang! 15:25
jlaska jeff_hann: kparal yeah good suggestions 15:25
jlaska jskladan: take care! 15:25
jskladan jlaska: thanks, will do my best 15:26
jlaska kparal: jeff_hann: I can take an action to follow-up w/ maxamillion after the meeting 15:26
* kparal brb in 2min 15:26
jeff_hann jlaska: a page where the exact criteria needed would be useful 15:26
jlaska jeff_hann: yeah I agree 15:26
jlaska I believe we started that page a few weeks back, but that might just need to be refreshed 15:27
jeff_hann jlaska: and instructions as how/what to fill in TRAC 15:27
jlaska #info a page where exact criteria needed for proventesters would be useful 15:27
jlaska jeff_hann: in TRAC? 15:27
jlaska jeff_hann: oh for applying to the group? 15:27
jeff_hann jeff_hann: yeah 15:27
jlaska #info provide a TRAC ticket template for mentor requests 15:27
jlaska #action jlaska to follow-up w/ maxamillion after meeting 15:28
jlaska for any other ideas that come to folks, please feel free to reply to the meeting minutes I send out 15:28
jlaska next topic ... 15:28
jlaska #topic Package Acceptance Test Plan check-in 15:29
jeff_hann jlaska: of course, I would like to join the proventesters group; been slackin' recently. 15:29
* kparal back 15:29
jlaska kparal: hey, do you want to give an update on this topic? 15:29
kparal sure 15:29
jlaska #chair kparal 15:29
zodbot Current chairs: jlaska kparal 15:29
kparal #link User:Kparal/Proposal:Package_update_acceptance_test_plan 15:29
kparal so, I posted a few last questions about the test plan and a call for comments 15:30
kparal #link 15:30
jlaska kparal: thanks for picking that back up ... I think I've got a few UNREAD's to read still on that thread 15:30
kparal from discussion with jlaska and jkeating I changed a few definitions 15:30
kparal so thanks for all comments 15:31
kparal I believe the test plan should be final now 15:31
* jlaska loves your test categories 15:31
kparal if no more comments come 15:31
jlaska mandatory, introspection, advisory :) 15:31
kparal one remaining item is to create separate wiki page for each test case 15:31
kparal #link 15:32
kparal and we can start to just implement it :) 15:32
kparal alright, that would be it, I believe 15:32
jlaska yay! 15:32
jlaska kparal: thanks for the updates ... anything you'd like to track here for next week? 15:33
kparal nope, I would say it's complete (nearly) :) 15:33
jlaska awesome, nice work 15:33
jlaska okay, the next planned topic I had was for AutoQA 15:33
jlaska but we're low on AutoQA folks today 15:34
jlaska #topic AutoQA update 15:34
jlaska kparal: anything you'd like to note for this week? 15:34
kparal I can say a few words for jskladan 15:34
jlaska kparal: great, please go for it! 15:34
kparal he created a test suite for resultdb API 15:34
kparal and made some first draft of implementing the API 15:34
kparal and of course the test suite failed, so he's now deep in solving the issues :) 15:35
kparal but we could have some first attempts for API implementation soon 15:35
kparal at least from what I caught 15:35
kparal ok, as for other topics, no big development that I know of 15:36
kparal so, let's move it to open discussion 15:36
kparal #topic Open Floor 15:37
kparal do you have anything you want to discuss today? 15:37
kparal how it happens that when I'm the chairman the meeting is always so fast? :) 15:39
kparal ok, last minute and then I'll end the meeting 15:40
jeff_hann kparal: today there only few attendees 15:40
jeff_hann *there are 15:40
kparal jeff_hann: I see. everyone on holiday or something :) 15:40
jlaska kparal: you're much better at moving the meeting along than I am! :D 15:40
* jlaska has mollases fingers 15:41
kparal ok, so thanks everyone for comming in, have a nice day! 15:41
kparal #endmeeting 15:41

Generated by 2.7 by Marius Gedminas - find it at!