This page documents the Standard Operating Procedures for the Fedora Quality Assurance (QA) team.
The SOP section contains a list of tasks the Fedora QA team provides for the project. Current QA team members can add tasks they know about and list steps to complete the task as well as issues to consider. This is a great way to make sure that individuals aren't the only ones that can fix a problem. Ideally, every task the QA team performs should be documented by an SOP, particularly those that are part of the release process and listed on the release calendar.
The SOP section of the wiki is left in the public because it is our hope that others in the community will add common problems, fix our steps and just in general look over what we're doing and help us when we're doing something stupid. This is a wiki and in true wiki fashion we encourage anyone interested to go over our processes with a fine tooth comb. It'll make us better and we'll probably learn something in the process. General rule, make change first, ask questions later. Many people are watching the wiki so if something is not right, we'll fix it or revert the page.
Pages in category "QA SOPs"
The following 20 pages are in this category, out of 20 total.
- QA:SOP becoming a sponsor
- QA:SOP Blocker Bug Meeting
- QA:SOP blocker bug process
- QA:SOP blocker tracker process
- QA:SOP compose request
- QA:SOP freeze exception bug process
- QA:SOP IRC meeting process
- QA:SOP new member welcome
- QA:SOP package test plan creation
- QA:SOP Rawhide Acceptance Test Event
- QA:SOP test case creation