Docs QA Procedure

Work Flow

1. Problem is identified
2. Bug is filed in Bugzilla
3. Someone fixes the bug and submits a patch to Bugzilla (same ticket) for consideration
   1. Procedure
      1. Create a new local branch for you to work: git checkout -b patch_for_BZ_<bug #>
      2. Make your changes in your new branch.
      3. Once you have committed your changes create your patch: git format-patch master --stdout > BZ<bz number>.patch
4. Filer confirms the patch fixes the problem
5. Bug goes to Docs QA (Bug set to "ON QA")
6. Docs QA checks the items documented in the Docs QA Review Guidelines in the patch
7. Docs QA sets ticket as "VERIFIED"
8. Owner applies the fix to the master branch.
   1. Check for errors before applying: git apply --check BZ<bz number>.patch
   2. If no errors, apply the patch: git am --signoff < BZ<bz number>.patch
9. Push the changes to the remote repo.
   1. If there has been no action from the QA after 10 days, the Owner contacts QA Wrangler (see below).
   2. If there has been no action from the QA after two weeks, the Owner applies the fix without QA approval.
10. Owner publishes the new version, closes bug
    1. 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.

Notes

1. Docs components with no specified QA contact will be QA'ed by the docs-qa mailing list
2. Patches should not be QA'ed by the component's owners or other regular contributors.
3. 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.

QA Wrangler

The Docs QA Wrangler will be a quasi-official position within Fedora Docs. The person who volunteers for this task will be responsible for:

1. Prodding assignees about stale tickets
2. Reporting regularly to the Docs groups about the ticket state (aggregate data on count, severity, status, etc)
3. ensuring QA contacts are assigned for bugzilla components
4. Performing spot checks on tickets to see if they follow the QA process and make determinations about the process' effectiveness.
5. Opening tickets for new Features to ensure major changes to Fedora are reflected in each guide.
6. Wrangling external review of their own commits