From Fedora Project Wiki
Attendees
People present (lines said)
Unable to attend:
- Rhe (hopefully sleeping)
Agenda
- Proposed meeting agenda
- [FIXME MeetBot summary]
Previous meeting follow-up
- jlaska to prep F15 test day wiki and request ideas on test@
- Nirik to start discussion on test list related to updates ideas (see http://lists.fedoraproject.org/pipermail/test/2010-November/095756.html)
Many ways to get involved in QA ...
Call for Test Days
- Owner
- jlaska
- Summary
- Call for ideas/owners for Fedora 15 QA/Test_Days
- Monitor list of approved features for ideas
- AdamW initiated GNOME3 discussion on desktop@ list
- Next steps ...
Create fedora-qa ticket
Python script communicating with bugzilla
- Owner
- Bruno
- Tune existing python scripts to detect UNTESTED blocker bugs
- Next steps ...
- See
fedora-qa ticket#89
Requirements review for Fedora test case management
- Owner
- rhe
- Requirements review for Fedora test case management
- Next steps ...
- See
fedora-qa ticket#152
Critical Path test case development
AutoQA Update
- Owner
- kparal
- Summary
- Updated roadmap wiki at https://fedoraproject.org/wiki/AutoQA_Roadmap
autoqa ticket#244(fas.conf) now in master - http://git.fedorahosted.org/git/?p=autoqa.git;a=commit;h=1b1d73030401a5859751b871043c15a2f8877064- mkrizek working on
autoqa ticket#205, see mkrizek branch (http://git.fedorahosted.org/git/?p=autoqa.git;a=shortlog;h=refs/heads/mkrizek) - Wwoods working on
autoqa ticket#248-- bad things happen if -pending set changes while test is running - Next steps ...
- Wwoods posting blog article explaining the need for
autoqa ticket#248 - Depcheck may need to be updated to provide bodhi feedback for each
$basearch - Jskladan rewriting bodhi watcher to work with depcheck (encountering depcheck issues)