Modern QA2026Release Workflow for QA — tiles
Log inJoin
46 / 57 · 17 Git & Version Control · Tagging and Releases← prev⊞ allnext →☰ Read as one page

6.6Release Workflow for QA

A typical QA-involved release workflow:

  1. Feature freeze: No new features on the release branch. Only bug fixes.
  2. Run full regression: Execute the complete test suite (automated + manual exploratory).
  3. Document results: Update the release checklist with test results.
  4. Create release candidate tag: v2.4.0-rc1
  5. Deploy RC to staging: Smoke test in a production-like environment.
  6. Sign-off: QA approves the release based on defined criteria.
  7. Tag the release: v2.4.0 with test result metadata.
  8. Deploy to production: Run post-deploy smoke tests.
  9. Monitor: Watch error rates and performance metrics for 24-48 hours.