As always, minutes and IRC transcript available at
https://fedoraproject.org/wiki/QA/Meetings/20110117
TOPIC: Previous meeting follow-up
===========================================
1. Bodhi feedback patch from fcami (see {{Ticket|infrastructure|
701}} awaiting review
* No updates on
https://fedorahosted.org/pipermail/bodhi/2010-December/000543.html
* jlaska will ping lmacken after meeting
TOPIC: Update on critpath test definition (ticket#154)
======================================================
1. The new system has gone public (see announcement at
http://lists.fedoraproject.org/pipermail/test-announce/2011-January/00017...)
2. Adamw started converting existing test cases to the new category
system, about half of our existing test cases done now
3. Adamw mailed infrastructure list to discuss the possibility of
adding a mediawiki extension which would allow multi-category
search (see
http://lists.fedoraproject.org/pipermail/infrastructure/2011-January/0098...)
4. The team discussed the possibility of adding multi-category
searching to the python-simplemediawiki API
5. Next steps ...
* Need to determine if/how to handle Category recursion on
the wiki
* IDEA: Discuss new test case SOP and wiki organization at
FUDCon Tempe
TOPIC: Latest and greatest on autoqa-0.4.4
===========================================
1. Simplified the test object template a bit by using
'self.__class__' where possible - ''So easy, a three year old
can do it'' (see
https://fedorahosted.org/pipermail/autoqa-devel/2011-January/001494.html)
2. clumens installer branch merged - New git-post-receive hook and
several installer tests (anaconda_checkbot, anaconda_storage and
compose_tree) (see
https://fedorahosted.org/pipermail/autoqa-devel/2011-January/001473.html)
3. mkrizek implemented logging support and unittest execution
support now in separate branches and will be merged once we have
a little time to review it (see
https://fedorahosted.org/autoqa/ticket/196 [logging] and
https://fedorahosted.org/autoqa/ticket/258 [unittest])
4. jskladan adjusted his 'new_koji_watcher' patch and the debate
ensued (see
https://fedorahosted.org/pipermail/autoqa-devel/2011-January/001485.html)
5. wwoods posted 'depcheck' patch (see
https://fedorahosted.org/pipermail/autoqa-devel/2011-January/001512.html
6. hongqing researching anaconda virtio support and integrating
that into rats_install/install.py (see
https://fedoraproject.org/wiki/Anaconda/Logging)
7. Next steps ...
* Review outstanding patches and merge into master
* Resolve remaining outstanding tickets for for
autoqa-0.4.4.
TOPIC: Update on TCMS nitrate analysis (ticket#152)
===================================================
1. TCMS Use Cases available at
https://fedoraproject.org/wiki/Rhe/tcms_use_cases
* Rhe regrouped the use cases by general and main test
events(runs) use cases. The general cases cover the
basic uses of wiki, and the events cases covers the
detailed certain steps for organizing the events.
2. Wiki and Nitrate comparison available at
https://fedoraproject.org/wiki/Rhe/tcms_Comparison
* The comparison is grouped according to the use cases. It
has overlaps between each other which I need to further
update. But the basic idea is shown, please review them
and welcome to provide any comments about the grouping
idea/design format/contents.
3. Next steps ...
* HELP: - Feedback needed ... last chance!
* Identify and prioritize MUSTHAVE and SHOULDHAVE features
* Begin roll-out of staging server for testing during
Fedora 15
OPEN DISCUSSION: Media_Handout_Requirement
===================================================
1. Viking-Ice drew attention to recent advisory board discussion on
SPINs and test plans (see
http://lists.fedoraproject.org/pipermail/advisory-board/2011-January/0102...)
2. A proposed requirements is available for review at
https://fedoraproject.org/wiki/Media_Handout_Requirements
3. Next steps ...
* HELP: - volunteers welcome - need to adjust current
draft to match QA workflow
* Post feedback to
https://fedorahosted.org/fedora-qa/ticket/164
OPEN DISCUSSION: IDEA - Anyone interested in data mining smolt?
===============================================================
1. In preparation for upcoming Xorg and gnome-shell test days, we
could really use help massaging smolt data
2. The goal -- figure out a way to get a raw dump of all graphics
cards out of smolt, then categorize them into generations, then
set up queries that abstract out the generations, so we can just
say ''find all cards in NVIDIA generation foo''
3. See adamw's blog post at
http://www.happyassassin.net/2011/01/17/potential-project-for-someone-gra...
4. Next steps ...
* Searching for a volunteer
OPEN DISCUSSION: 2010-01-27 - Network Device Naming test day
===============================================================
1. Just a reminder that F15 Test Days are starting up next week
2. Coming soon ...
https://fedoraproject.org/wiki/Test_Day:2011-01-27_Network_Device_Naming_...
3. Next steps ...
* Rename test cases to comply with SOP
* Adjust test cases to use {{template:QA/Test_Case}}
* Add instructions to identify if you have applicable
hardware to participate
OPEN DISCUSSION: Advertise QA team services to devel-announce
===============================================================
1. Viking-Ice suggested sending a reminder to
devel-announce(a)lists.fedoraproject.org reminding maintainers of
the services offered by the Fedora QA team
2. Not enough time to complete idea, continue discussion on list
ACTION ITEMS
===================================================
1. jlaska - check-in with lmacken on
http://lists.fedoraproject.org/pipermail/devel-announce/2011-January/0007...
2. adamw - follow-up on advisory-board thread on media requirements
for spins
(
http://lists.fedoraproject.org/pipermail/advisory-board/2011-January/0102...).
3. Open to anyone
1. Contribute feedback to upcoming Network Device naming
test day
2. Participate in SMOLT data mining project
3. Help migrate wiki test cases to new category format
4. Add feedback to TCMS proposals (use case and comparison)