#228: SOPs for Everything -----------------------+---------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Fedora 17 Component: Wiki | Version: Resolution: | Keywords: -----------------------+---------------------------------------------------- Comment (by adamwill):

Looking at the F16 quality calendar:

http://rbergero.fedorapeople.org/schedules/f-16/f-16-quality-tasks.html

here's a list of tasks (minus multiple instances of the same task) and the SOP status:

* Rawhide Acceptance Test Plan: SOP in draft - https://fedorahosted.org /fedora-qa/ticket/227 * Blocker Meeting: SOP available - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting * Daily Review & Notification of Open Alpha Blocker Bugs: no SOP (AFAIK) * Release Notes: this is a docs task in our schedule for information, sorta documented at https://fedoraproject.org/wiki/Docs_Project_workflow#Release_Notes * Test 'Test Compose', Test Candidate: SOP available - https://fedoraproject.org/wiki/QA/SOP_Release_Validation_Test_Event * Go/No-Go Meeting: SOP available - https://fedoraproject.org/wiki/Go_No_Go_Meeting * Release Readiness Meeting: no SOP (AFAIK) - this is a project-wide meeting so we don't own it * NVR Update Check testing: no SOP, is a dead letter ATM and superseded by AutoQA upgradepath testing

I think that's everything, so I'd say we're actually doing pretty well. There's only a couple of action items there.

#228: SOPs for Everything -----------------------+---------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Fedora 17 Component: Wiki | Version: Resolution: | Keywords: -----------------------+---------------------------------------------------- Comment (by jlaska):

Yeah, we kind of handled the daily blocker on a as-needed basis. For Fedora 15, it never really got to PANTSCON-1 alert level. I'm not sure if we need this in the QA schedule anymore. Or perhaps it might make more sense moving this concept into some general SOP on how to help move bugs along without annoying maintainers too much (but just enough).

#228: SOPs for Everything -----------------------+--------------------------------- Reporter: adamwill | Owner: adamwill Type: task | Status: new Priority: major | Milestone: Undetermined Future Component: Wiki | Version: Resolution: | Keywords: Blocked By: | Blocking: -----------------------+--------------------------------- Changes (by adamwill):

* cc: test@… (added) * milestone: Fedora 18 => Undetermined Future