From Fedora Project Wiki

< QA‎ | Meetings

m (Initial draft)
 
m (Updated agenda)
Line 21: Line 21:


Upcoming test milestones:
Upcoming test milestones:
* 2010-03-18 - [[:Category:Fedora_13_Beta_TC_Test_Results|Test Beta 'Test Compose']]
* 2010-03-25 - [[:Category:Fedora_13_Beta_RC_Test_Results|Test Beta 'Release Candidate']] - '''<font color="blue">INPROGRESS</font>'''
** Jkeating and dlehman working together to determine what packages to include in 'test compose' ... expected end of day today
* 2010-03-31 - Beta Go/No-Go Meeting (20:00 EST)
* 2010-03-25 - [[:Category:Fedora_13_Beta_RC_Test_Results|Test Beta 'Release Candidate']]


Upcoming test days:
Upcoming test days:
* 2010-03-25 - [[Test_Day:2010-03-25_Printing|Printing Test Day]] -- [[User:twaugh|twaugh]]
* 2010-03-30 - [[Test_Day:2010-03-30_SSSDByDefault|SSSD by default Test Day]] -- [[User:jlaska|jlaska]]
* 2010-03-30 - [[Test_Day:2010-03-30_SSSDByDefault|SSSD by default Test Day]] -- [[User:jlaska|jlaska]]
* 2010-04-01 - [[Test_Day:2010-04-01_ABRT|ABRT Test Day]] -- [[User:kparal|kparal]]
* 2010-04-01 - [[Test_Day:2010-04-01_ABRT|ABRT Test Day]] -- [[User:kparal|kparal]]
 
* 2010-04-08  - [[Test_Day:2010-04-08_Virtualization|Virtualization Test Day]] -- [[User:jforbes|jforbes]] + [[User:mdoyle|mdoyle]]
Wwoods noted it would be great if there was an SOP available so that direct involvement with QA wasn't required. Jlaska pointed to https://fedoraproject.org/wiki/QA/SOP_Test_Day_management


== Updates Testing ==
== Updates Testing ==

Revision as of 14:47, 29 March 2010

Attendees

People present (lines said)

Regrets:

Agenda

Previous meeting follow-up

  1. wwoods and adamw to discuss tooling needs for priv esc. test
  2. maxamillion will work on second draft of provenpackagers proposal
  3. adamw will provide a draft for the update test plan
  4. jlaska to post meeting time change request to test@l.fp.org

Fedora 13 test status

Upcoming test milestones:

Upcoming test days:

Updates Testing

There are some disparate efforts underway designed to improve the Updates testing workflow. Currently, the only defined process discusses using yum to enable updates-testing (see QA/Updates Testing). Jlaska asked the group for ideas on what tasks are needed to define a process by which testers can provide test feedback for updated packages.

Ideas included:

  • we need a policy/sop for the 'proventesters' group
  • we need a guide to providing updates-testing feedback for branched + released explaining what should be tested and how to give feedback
  • we need general guidance on that which applies to all packages; having specific instructions for some is also good, but the priority should be to define exactly what the acceptance testing is supposed to check
  • Improve documenting around using fedora-easy-karma

Open discussion - <Your topic here>

Adjust meeting time?

Kparal and jskladan asked whether the QA meeting time could adjust to keep the localtime the same, but change UTC. This would moving the meeting from 16:00 UTC to 15:00 UTC during spring+summer. No objections were made during the meeting, jlaska would raise the topic on the list as well.

Upcoming QA events

Action items