2010-05-17 - Fedora QA meeting recap
James Laska
jlaska at redhat.com
Mon May 17 17:06:03 UTC 2010
As always, minutes and IRC transcript available at
https://fedoraproject.org/wiki/QA/Meetings/20100517
= Attendees =
== People present (lines said): ==
1. jlaska (108)
2. wwoods (66)
3. kparal (23)
4. quaid (18)
5. maxamillion (12)
6. jskladan (2)
7. jeff_hann (2)
8. ianweller (1)
9. Viking-Ice (1)
== Regrets: ==
1. liam
2. rhe
3. adamwill
= Agenda =
* Proposed meeting agenda -
http://lists.fedoraproject.org/pipermail/test/2010-May/090980.html
* MeetBot summary -
http://meetbot.fedoraproject.org/fedora-meeting/2010-05-17/fedora-qa.2010-05-17-15.00.html
== Previous meeting follow-up ==
* No previous action items
== Fedora 13 RC#3 test status ==
Upcoming test milestones:
* 2010-05-18 - Fedora 13 Final Go/No-Go Meeting (20:00 EST)
Current test activities:
* Current_Installation_Test -
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
* Outstanding test results (i386): 4
* Outstanding test results (x86_64): 1
* Current_Desktop_Test -
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
* Outstanding test results: 32 (8 tests * 4 desktops)
* CommonBugs? -
https://bugzilla.redhat.com/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=CommonBugs%3F&sharer_id=141215
* 14 bugs
== Fedora 13 QA Retrospective ==
* You've heard me talk about it many times, but time is running
out to voice yours concerns and suggestions about Fedora 13
Testing. Be heard at
https://fedoraproject.org/wiki/Fedora_13_QA_Retrospective
== Summer of Code ==
* Last week, kparal asked the group whether there was interest in
QA Summer of code projects. Feedback on
https://fedoraproject.org/wiki/QA:Summer_of_Code_Ideas was
requested by May 13, 2010. No additional feedback given.
* Karsten informed the group that another summer of code slot
would be available from Sept - Feb. QA could still participate
then.
= Open Discussion =
== Ideas to make QA sexy ==
* Adam Miller expressed an interest in working with the Design
team to come up with some swag we could award exceptional QA
members with. The discussion led to the selection process for
awarding swag. Some thoughts included:
* a method for packagers/maintainers to recognize an
exceptional QA effort (in triaging, testing or reporting
bugs)
* recognizing notable QA contributions based on several
metrics (bugs reported, karma provided, bug triage,
mailing list feedback, QA namespace wiki
contributions).
== AutoQA post-bodhi-update update ==
* Will Woods information the team of his progress on writing a
post-bodhi-update watcher script.
* The basic purpose of post-bodhi-update is to fire autoqa tests
whenever a maintainer uses bodhi to request an update be moved
into the testing or stable repos. Code is available in
autoqa.git wwoods branch [1].
* Will reviewed several limitations with the watcher, and asked
for feedback on resolving.
* Will expects to have watcher completed this week, and remaining
tasks (autoqa hook code, test templates and hello-bodhi
proof-of-concept test) completed next week.
[1]
http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=hooks/post-bodhi-update/watch-bodhi-requests.py;hb=wwoods
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/test/attachments/20100517/02c893cd/attachment.bin
More information about the test
mailing list