Template — Release Checklist

Scope

  • Release/version/commit identified.
  • User-visible and operator-visible changes summarised.
  • Compatibility impact reviewed.
  • Configuration/data migrations documented.

Validation

  • Required unit/integration suites pass.
  • Runtime/smoke tests pass for claimed compatibility targets.
  • Build artifacts correspond to the intended commit.
  • Upgrade path tested where applicable.

Operations

  • Backup/rollback boundary understood.
  • Required credentials/access available through approved systems.
  • Monitoring/health check prepared.

Documentation

  • Current Status page updated.
  • Commands/configuration/version tables updated if changed.
  • New limitations or migration notes documented.
  • Roadmap items moved into reference documentation when completed.

Post-release

  • Deployment verified from the user perspective.
  • Logs/metrics checked for regressions.
  • Temporary migration notes/toggles scheduled for cleanup if applicable.
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9