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
 * 4) 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.
 * 5) Filer confirms the patch fixes the problem
 * 6) Bug goes to Docs QA (Bug set to "ON QA")
 * 7) Docs QA checks the items documented in the Docs QA Review Guidelines in the patch
 * 8) Docs QA sets ticket as "VERIFIED"
 * 9) Owner applies the fix to the master branch.
 * 10) If there has been no action from the QA after two weeks, the Owner applies the fix without QA approval.
 * 11) Owner publishes the new version, closes bug
 * 12) 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.