- Problem is identified
- Bug is filed in Bugzilla
- Someone fixes the bug and submits a patch to Bugzilla (same ticket) for consideration
- If a fix is needed for the current release, owner says so and requests immediate QA action. Patch is applied to current release and master.
- Filer confirms the patch fixes the problem
- Bug goes to Docs QA (Bug set to "ON QA")
- Docs QA checks the items documented in the Docs QA Review Guidelines in the patch
- Docs QA sets ticket as "VERIFIED"
- Owner applies the fix to the master branch.
- If there has been no action from the QA after 10 days, the Owner contacts QA Wrangler (see below).
- If there has been no action from the QA after two weeks, the Owner applies the fix without QA approval.
- Owner publishes the new version, closes bug
- When a Guide is branched for release, all patches can be included, even if they are still "ON_QA," but the bug remains ON_QA so the QA contact can verify the fix eventually.
- Docs components with no specified QA contact will be QA'ed by the docs-qa mailing list
- Patches should not be QA'ed by the component's owners or other regular contributors.
- The Docs lead is in charge of nagging the docs-qa mailing list about open QA tasks since the nag feature of BZ isn't enabled.
The Docs QA Wrangler will be a quasi-official position within Fedora Docs. The person who volunteers for this task will be responsible for:
- Prodding assignees about stale tickets
- Reporting regularly to the Docs groups about the ticket state (aggregate data on count, severity, status, etc)
- ensuring QA contacts are assigned for bugzilla components
- Performing spot checks on tickets to see if they follow the QA process and make determinations about the process' effectiveness.
- Opening tickets for new Features to ensure major changes to Fedora are reflected in each guide.
- Wrangling external review of their own commits