From Fedora Project Wiki

< QA‎ | Meetings

Revision as of 14:22, 3 May 2010 by Jlaska (talk | contribs) (Update notes)

Attendees

People present (lines said):

Regrets:

Agenda

  • [FIXME Proposed meeting agenda]
  • [FIXME MeetBot summary]

Previous meeting follow-up

  • current members of the 'qa' group ... apply to 'proventesters'
  • jlaska to follow-up w/ maxamillion after meeting

Fedora 13 RC test status

Upcoming test milestones:

  • 2010-04-29 - Test 'Final' Test Compose -- INPROGRESS
  • 2010-04-30 - Final Blocker Meeting (f13blocker) #3 (recap)
  • 2010-05-05 - Final Blocker Meeting (f13blocker) #4
  • 2010-05-06 - Test 'Final' RC

No upcoming test days:

Important.png
Fedora 13 QA Retrospective
Ideas have already been coming in since F-13-Alpha. It's not too early to note QA issues you felt where handled well, or could have been improved. Your ideas will be used during F-14 QA goal planning. Voice your comments at Fedora_13_QA_Retrospective.

Proventesters check-in

  • The team discussed possible next steps, including ...
    • Mass subscribing current qa group members to proventesters
    • Updating bodhi to rely on proventesters group for critpath feedback
  • In order to move QA/JoinProvenTesters:Draft out of draft, what else is needed?
    • Document recommended experience for proventesters ?
    • Mentor requests?

Package Acceptance Test Plan check-in

  • Last week, we discussed next steps ...
    • Remove draft status
    • Document each test case (see ticket#62)

AutoQA check-in

There has been a lot of AutoQA activities in recent weeks, jlaska asked the group to walk through some highlights.

  • Kparal provided some updates from jskladan on the results database efforts..
    • First draft of implementing the resultsdb API
    • Test suite for resultsdb API created

Open discussion - <Your topic here>

Upcoming QA events

Action items

IRC Transcript