Attendees
People present (lines said)
- adamw (56)
- wwoods (23)
- jlaska (17)
- kparal (14)
- skvidal (4)
Regrets:
Agenda
Previous meeting follow-up
- adamw to offer some guidance on how to handle hardware/local_configuration specific bugs
DONE -- see Blocker_Bug_FAQ#What_about_hardware_and_local_configuration_dependent_issues.3F
- jlaska to post recommendations on F-12 QA retrospective
INPROGRESS -- expect to have this cleaned up in the next day or so (see Fedora_12_QA_Retrospective#Recommendations).
Enhancing Release Criteria
- See Fedora_Release_Criteria
- Current status
As announced on the list, we completed the initial work on the criteria at FUDCon
- What's next?
No specific plans for further release criteria action.
Security Policy / Test Plan
- Initial kick-off - http://spot.livejournal.com/312216.html
- Current status
Adamw reported that he took the proposal to the security team as discussed during previous meeting, but hasn't received much feedback so far. Wwoods noted there was some discussion at FUDCon on instrumenting tests to detect when security changes have likely occurred for example ...
- new builds that use consolehelper or have suid binaries
- added or removed policykit files
The group felt this might make sense for a future rpmguard update.
- What's next?
Adamw will likely escalate the issue to FESCO for guidance.
AutoQA update
Wwoods talked about several AutoQA discussions that took place at FUDCon Toronto. Additionally, Will posted his slides for review (see http://wwoods.fedorapeople.org/files/AutoQA-FUDCon-Toronto-2009.odp). Some topics of discussion included:
- distro labels for test machines
- cleaner handling of 'noarch' tests like rpmlint/rpmguard
- Future AMQP (messaging bus) support
Wwoods also make progress on packaging his side-project ... hot-dog.
rpmguard integration
Kparal completed the integration of rpmguard into autoqa (see announcement). Kparal asked for feedback on the changes before he merges them. Specifically, if there are suggestions or recommendations to the test output format, Kparal is anxious for your feedback. Wwoods suggested collapsing similar results from different architectures into the same result.
deps/conflicts prevention
- See milestone - https://fedorahosted.org/autoqa/milestone/autoqa%20depcheck
Wwoods reiterated that not much actual *work* on autoqa, but plenty of good discussions. I expect we'll be writing up roadmaps and tickets and such for a while. Will has a much clearer idea for how to proceed now and will begin adding tickets into the trac roadmap.
Install automation
- Proposal from User:Liam and User:Rhe out for review ... see Is_anaconda_broken_proposal.
Jlaska informed the team that Liam and Hurry are looking for feedback on the definition of the 'problem space'. Jlaska plans to provide some commentary later today, but invited others to share their thoughts as well.
Jlaska suggested that a team gathering in the next week or so might be helpful to get everyone on the same page for F-13 test plan ideas.
Open discussion - <Your topic here>
F-13 Test Day Schedule
Adamw and jlaska briefly discussed the F-13 test day schedule and intentions for reaching out to F-13 feature owners (see Releases/13/FeatureList).
Upcoming QA events
- NA
Action items
- adamw to escalate security policy issue to fesco
- wwoods to keep an eye on plans for autoqa tests
- jlaska to set up a meeting to co-ordinate test plan changes for F13
- adamw and jlaska to look at setting up f13 test day process
IRC transcript
| adamw | #startmeeting 2009-12-14 QA meeting | 16:01 |
|---|---|---|
| zodbot | Meeting started Mon Dec 14 16:01:36 2009 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:01 |
| zodbot | Useful Commands: #action #agreed #halp #info #idea #link #topic. | 16:01 |
| * jlaska in read-only mode | 16:01 | |
| adamw | #topic gathering people | 16:02 |
| * kparal up and running | 16:02 | |
| adamw | who else is here? | 16:02 |
| * wwoods here! | 16:02 | |
| adamw | bueller? | 16:03 |
| adamw | alrighty, guess that's it | 16:04 |
| adamw | #topic previous meeting follow-up | 16:04 |
| adamw | so, two entries here | 16:04 |
| adamw | adamw to offer some guidance on how to handle hardware/local_configuration specific bugs - that's done, we included it into the blocker bug FAQ | 16:04 |
| adamw | #link Blocker_Bug_FAQ#What_about_hardware_and_local_configuration_dependent_issues.3F | 16:04 |
| adamw | anyone got any comments / rotten fruit on that? | 16:05 |
| jlaska | adamw: I like the bullet list at the end :) | 16:05 |
| jlaska | you know I like lists! | 16:05 |
| * adamw puts jlaska's gag back on ;) | 16:06 | |
| jlaska | okay ... no more constructive feedback then! :P | 16:06 |
| adamw | alright then | 16:06 |
| adamw | second item - jlaska to post recommendations on F-12 QA retrospective | 16:06 |
| adamw | listed as "INPROGRESS -- expect to have this cleaned up in the next day or so" | 16:07 |
| adamw | #link Fedora_12_QA_Retrospective#Recommendations | 16:07 |
| adamw | anything to add, silentlaska? | 16:07 |
| * jlaska can't speak over the duct tape | 16:08 | |
| adamw | that's how we like it | 16:08 |
| jlaska | hah | 16:08 |
| adamw | alrighty then | 16:09 |
| adamw | #topic enhancing release criteria | 16:09 |
| adamw | #info as announced on the list, we completed the initial work on the criteria at FUDCon | 16:10 |
| adamw | #link Fedora_Release_Criteria | 16:10 |
| adamw | jlaska asks 'what's next?' | 16:10 |
| adamw | well, we received some feedback on possible changes, i merged some of that in | 16:11 |
| adamw | anyone have anything else they'd like to add? | 16:11 |
| jlaska | they look awesome, looking forward to referencing them during F-13 testing | 16:11 |
| adamw | we didn't get any feedback from any spin SIGs yet | 16:12 |
| adamw | welp, if we've got nothing to add then... | 16:13 |
| adamw | #info no specific plans for further release criteria action | 16:14 |
| adamw | #topic security policy / test plan | 16:14 |
| adamw | jlaska provides: | 16:14 |
| adamw | #link http://spot.livejournal.com/312216.html | 16:14 |
| adamw | for a starting point, which is the same post we've looked at before. | 16:14 |
| adamw | from my side the status on this is that i took it to the security team, as suggested, but haven't received much feedback | 16:15 |
| adamw | so i will probably escalate it to fesco without a proposed policy | 16:15 |
| adamw | does anyone else have any status on this? | 16:15 |
| jlaska | no updates from me ... just wanted to check-in and see where it was and what (if anything) it needed to move forward | 16:16 |
| wwoods | no, although there was some discussion at FUDCon about how to get autoqa tests to notice new builds that use consolehelper or have suid binaries | 16:16 |
| adamw | that would be helpful indeed | 16:16 |
| jlaska | ^^^ rpmguard? | 16:16 |
| adamw | and we could throw a check for policykit files into rpmguard | 16:16 |
| adamw | (added removed or changed) | 16:16 |
| wwoods | yep - that was part of the answer, certainly | 16:16 |
| adamw | alright then... | 16:18 |
| adamw | #action adamw to escalate security policy issue to fesco | 16:18 |
| adamw | #action wwoods to keep an eye on plans for autoqa tests | 16:18 |
| adamw | the moment you've no doubt been waiting for: | 16:20 |
| adamw | #topic autoqa update | 16:20 |
| adamw | take it away! | 16:20 |
| wwoods | so! for those who weren't there, I spent a good deal of FUDCon talking about AutoQA. Whee! | 16:20 |
| wwoods | here's the slides from the presentation: http://wwoods.fedorapeople.org/files/AutoQA-FUDCon-Toronto-2009.odp | 16:21 |
| wwoods | there are notes in the slide deck that explain the content further | 16:21 |
| adamw | #link http://wwoods.fedorapeople.org/files/AutoQA-FUDCon-Toronto-2009.odp | 16:21 |
| kparal | what the hot dog stands for? | 16:22 |
| wwoods | I've got some good ideas for needed improvements to autoqa - distro labels for test machines, cleaner handling of 'noarch' tests like rpmlint/rpmguard, and future AMQP (messaging bus) support | 16:22 |
| wwoods | kparal: the hot dog is everyone's new best friend | 16:23 |
| kparal | certainy would like to have it near me | 16:23 |
| wwoods | he was some artwork from an oooold version of anaconda that's been in the anaconda source tree for like.. almost 10 years | 16:23 |
| kparal | i see | 16:24 |
| wwoods | he keeps popping up in the generic (non-trademark) artwork and everyone loves him | 16:24 |
| wwoods | see also: http://wwoods.fedorapeople.org/hot-dog/ | 16:24 |
| kparal | nice! | 16:24 |
| wwoods | anyway: not much actual *work* on autoqa, but plenty of good discussions. I expect we'll be writing up roadmaps and tickets and such for a while | 16:25 |
| wwoods | the other major thing we talked about was the autoqa depcheck test | 16:25 |
| wwoods | which already has a milestone: https://fedorahosted.org/autoqa/milestone/autoqa%20depcheck | 16:25 |
| wwoods | again, not much work, but a lot of talk, and I have a much clearer idea of how that will work | 16:26 |
| wwoods | but I wouldn't expect to see it finished before the new year. | 16:26 |
| kparal | my turn? | 16:28 |
| wwoods | go for it! | 16:28 |
| skvidal | wwoods: I had a talk with the rpm folks about some of this stuff | 16:29 |
| skvidal | wwoods: it's on my list to look at a way to speed up repoclosure | 16:29 |
| * kparal taking microphone | 16:30 | |
| kparal | alright, I have worked on the rpmguard integration into autoqa and I have posted the first results. it's in the public kparal/rpmguard-integration branch, you can try it (please do) | 16:30 |
| wwoods | skvidal: cool, we'll talk later/elsewhere | 16:30 |
| kparal | I have posted announcement here: https://fedorahosted.org/pipermail/autoqa-devel/2009-December/000047.html | 16:30 |
| skvidal | cool | 16:30 |
| skvidal | kparal: sorry | 16:30 |
| wwoods | kparal: oh nice! | 16:30 |
| kparal | there is an example output in the link, click on that and have a look | 16:31 |
| kparal | wwoods: if you think the output format should be different, please let me know | 16:31 |
| wwoods | nice. we might want to work out a way to merge the results when it's the same for each arch | 16:31 |
| kparal | yes, that would certainly be good to consider | 16:31 |
| * kparal filing a ticket in his head | 16:32 | |
| kparal | so, that's from me. I hope I gather some feedback on the list :) | 16:32 |
| adamw | ah, HeadTrac, that sturdy workhorse of an issue tracking system =) | 16:33 |
| wwoods | kparal: awesome work. I'm really excited about this! | 16:33 |
| adamw | anything else on autoqa? | 16:33 |
| jlaska | I just wanted to point out some of the efforts liam and rhe have been working on | 16:34 |
| wwoods | at some point we'll need to decide on QA policy about which changes are just warnings and which mean TEST FAILURE | 16:34 |
| jlaska | #link Is_anaconda_broken_proposal | 16:34 |
| wwoods | now that rpmguard is apparently up and running that'll be very soon. | 16:34 |
| jlaska | Liam and Hurry are putting the finishing touches on the 'problem description' | 16:35 |
| jlaska | I've got a few comments to add to it later today, but the next step will be to coordinate test plan changes for F-13 | 16:35 |
| jlaska | I know adamw's got some good thoughts, as do Liam and Hurry ... so I'd like to setup a time for the group (and anyone else interested) to hash through it online | 16:36 |
| jlaska | that's it from me | 16:36 |
| adamw | alright | 16:37 |
| adamw | #action jlaska to set up a meeting to co-ordinate test plan changes for F13 | 16:37 |
| adamw | we also need to get on top of the test day schedule - start sending out emails asking people to request test days | 16:37 |
| adamw | set up some of our recurring ones | 16:37 |
| jlaska | let's set that up as check-in for next week's meeting? | 16:37 |
| adamw | yeah | 16:38 |
| adamw | #action adamw and jlaska to look at setting up f13 test day process | 16:38 |
| adamw | anything else? | 16:39 |
| * jlaska puts duct tape on | 16:39 | |
| adamw | diddly-doo, diddly-doo, diddly-doo, doo! | 16:40 |
| adamw | thanks everyone for coming | 16:40 |
| adamw | #endmeeting | 16:40 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!