m (Updated attendees) |
m (Updated notes) |
||
| Line 31: | Line 31: | ||
* See [[Fedora_Release_Criteria]] | * See [[Fedora_Release_Criteria]] | ||
* ''Current status'' | |||
What's next? | 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 == | == Security Policy / Test Plan == | ||
* Initial kick-off - http://spot.livejournal.com/312216.html | * Initial kick-off - http://spot.livejournal.com/312216.html | ||
* Current status | * ''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 == | == 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 ... [http://wwoods.fedorapeople.org/hot-dog/ hot-dog]. | |||
=== rpmguard integration === | === rpmguard integration === | ||
* See milestone - https://fedorahosted.org/autoqa/milestone/Package%20update%20tests | * See milestone - https://fedorahosted.org/autoqa/milestone/Package%20update%20tests | ||
Kparal completed the integration of rpmguard into autoqa (see [https://fedorahosted.org/pipermail/autoqa-devel/2009-December/000047.html 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 === | === deps/conflicts prevention === | ||
* See milestone - https://fedorahosted.org/autoqa/milestone/autoqa%20depcheck | * 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 === | === Install automation === | ||
* Proposal from [[User:Liam]] and [[User:Rhe]] out for review ... see [[Is_anaconda_broken_proposal]]. | * 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> == | == Open discussion - <Your topic here> == | ||
| Line 63: | Line 93: | ||
= Action items = | = 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 = | = IRC transcript = | ||
Revision as of 17:48, 14 December 2009
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>
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