#fedora-meeting: Fedora QA Meeting

Meeting summary

1. roll call (adamw, 16:01:31)
   
2. previous meeting follow-up (adamw, 16:05:49)
   1. no action items from previous meeting on which to follow up (adamw, 16:07:14)
   
   
3. FUDCon NA hackfest planning (adamw, 16:07:26)
   1. https://www.redhat.com/archives/anaconda-devel-list/2011-November/msg00055.html (adamw, 16:09:14)
   2. We have room 3 on Sunday from 0900 to 1400 (j_dulaney, 16:10:44)
   3. plan is to get anaconda and qa teams together to work on testing the new installer UI (adamw, 16:12:06)
   4. if we need things coded into the UI to make it testable we have to say so now (adamw, 16:13:38)
   5. ACTION: kparal to try and co-ordinate all involved in writing installer autoqa tests together to determine if we need any hooks in the new anaconda code (adamw, 16:19:48)
   
   
4. Fedora 17 Test Day planning (adamw, 16:20:42)
   1. ACTION: j_dulaney to take a shot at co-ordinating F17 test days, thanks! (adamw, 16:27:33)
   
   
5. Upcoming QA events (adamw, 16:28:47)
   1. ACTION: adamw to get retrospective tickets filed and summary mailed this week (adamw, 16:30:09)
   2. ACTION: adamw to start an ml thread proposing changes to the tc dates for f17 schedule to be sent to rbergeron (adamw, 16:34:10)
   3. if you're planning on going to FUDCon please sign up, and if you need funding, file a ticket now (adamw, 16:36:50)
   
   
6. autoqa update (adamw, 16:37:04)
   1. autoqa 0.7.0 deployment still in planning (adamw, 16:43:34)
   2. autoqa test client hardware is still running F14, so needs to be upgraded (adamw, 16:43:45)
   
   
7. open floor (adamw, 16:46:36)
   
8. open floor - current QA priorities (adamw, 16:47:09)
   1. all outstanding tasks should have trac tickets by the end of the week, which will help with assignation / prioritization (adamw, 16:59:41)
   2. infrastructure team is calling for testing of a rhel6-based fedorahosted.org , see nirik's link for more details (adamw, 17:02:36)
   
   
9. open floor (adamw, 17:02:44)

Action items

1. kparal to try and co-ordinate all involved in writing installer autoqa tests together to determine if we need any hooks in the new anaconda code
2. j_dulaney to take a shot at co-ordinating F17 test days, thanks!
3. adamw to get retrospective tickets filed and summary mailed this week
4. adamw to start an ml thread proposing changes to the tc dates for f17 schedule to be sent to rbergeron

Action items, by person

1. adamw
   1. adamw to get retrospective tickets filed and summary mailed this week
   2. adamw to start an ml thread proposing changes to the tc dates for f17 schedule to be sent to rbergeron
2. j_dulaney
   1. j_dulaney to take a shot at co-ordinating F17 test days, thanks!
3. kparal
   1. kparal to try and co-ordinate all involved in writing installer autoqa tests together to determine if we need any hooks in the new anaconda code
4. rbergeron
   1. adamw to start an ml thread proposing changes to the tc dates for f17 schedule to be sent to rbergeron

People present (lines said)

1. adamw (130)
2. j_dulaney (43)
3. kparal (31)
4. tflink (27)
5. red_alert (8)
6. rbergeron (7)
7. zodbot (6)
8. nirik (5)
9. jskladan (2)
10. brunowolff (1)
11. pschindl (1)