Release Readiness Checklist

Purpose

Provide the mandatory go or no-go checklist before manually creating a DSAMbayes release tag. It supports the normal quarterly release cycle; it does not require CI/CD or a rapid release cadence.

How to use this checklist

  1. Complete this checklist after running all release-quality gates.
  2. Record evidence paths for each item.
  3. If any mandatory item fails, decision is NO-GO.
  4. Copy final decision details into Release Sign-off Template.

Mandatory checklist

ID Check Pass criteria Evidence required
RL-01 Candidate commit fixed Single candidate commit hash selected and recorded, with matching sign-off metadata 00_release_identity/release_identity.txt, 40_signoff/sign_off_record.md
RL-02 Version metadata aligned DESCRIPTION version equals intended release version 00_release_identity/release_identity.txt
RL-03 Changelog aligned Top CHANGELOG.md section matches candidate scope 00_release_identity/changelog_top.md
RL-04 QG-1 lint passed Exit code 0, no lint failures 10_quality_gates/qg1_lint.log, 10_quality_gates/qg1_lint.exit
RL-05 QG-2 style passed Exit code 0, no style failures 10_quality_gates/qg2_style.log, 10_quality_gates/qg2_style.exit
RL-06 QG-3 tests passed Exit code 0, no test failures 10_quality_gates/qg3_tests.log, 10_quality_gates/qg3_tests.exit
RL-07 QG-4 Stan release evidence passed Exit code 0; diagnostic thresholds passed 10_quality_gates/qg4_stan_release_evidence.*
RL-08 QG-5 package check passed No ERROR; no unresolved WARNING 10_quality_gates/qg5_rcmdcheck.log, 10_quality_gates/qg5_rcmdcheck.exit
RL-09 QG-6 validate passed Exit code 0; required validate artefacts present 10_quality_gates/qg6_validate.*, 20_runner_artifacts/quality_gate_validate/
RL-10 QG-7 run passed Exit code 0; required run artefacts present 10_quality_gates/qg7_run.*, 20_runner_artifacts/quality_gate_run/
RL-11 QG-8 docs build passed Exit code 0; docs-site build completed 10_quality_gates/qg8_docs.*
RL-12 Dependency sources recorded Non-CRAN and file:// dependency sources, revisions, and portability decisions are recorded; no credentials are included 00_release_identity/dependency_sources.md
RL-13 Evidence bundle complete All mandatory evidence items present Evidence root directory
RL-14 Exceptions resolved or accepted All exceptions documented with owner and approval 40_signoff/sign_off_record.md
RL-15 Final sign-off recorded Decision, approver, and timestamp completed 40_signoff/sign_off_record.md

Required runner artefact checks

Validate artefacts that must exist:

  1. 20_runner_artifacts/quality_gate_validate/00_run_metadata/config.original.yaml
  2. 20_runner_artifacts/quality_gate_validate/00_run_metadata/config.resolved.yaml
  3. 20_runner_artifacts/quality_gate_validate/00_run_metadata/config.compiled.yaml
  4. 20_runner_artifacts/quality_gate_validate/00_run_metadata/session_info.txt

Run artefacts that must exist:

  1. 20_runner_artifacts/quality_gate_run/00_run_metadata/config.resolved.yaml
  2. 20_runner_artifacts/quality_gate_run/00_run_metadata/config.compiled.yaml
  3. 20_runner_artifacts/quality_gate_run/20_model_fit/model.rds
  4. 20_runner_artifacts/quality_gate_run/30_post_run/fitted.csv
  5. 20_runner_artifacts/quality_gate_run/30_post_run/observed.csv
  6. 20_runner_artifacts/quality_gate_run/40_diagnostics/diagnostics_report.csv

Decision rules

  1. GO only if every checklist item RL-01 to RL-15 passes.
  2. NO-GO if any mandatory item fails or evidence is incomplete.
  3. HOLD if no hard failure exists but final approval is pending.
  4. Tag creation is allowed only after GO decision is recorded.
  5. A NOTE or expected low-budget smoke-test sampler warning is not a blanket exception: its source and reviewer treatment must be recorded. QG-4 high-budget diagnostic-threshold failures always block release pending an explicit human decision.

Completion record template

Use this section when running the checklist.

Field Value
Release version <fill>
Candidate commit hash <fill>
Checklist executor <fill>
Checklist completion date (UTC) <YYYY-MM-DD>
Checklist result (GO/NO-GO/HOLD) <fill>
Evidence root path <fill>
Sign-off record path <fill>

Audit continuity reference

For programme-level historical traceability, also review:

  • refactoring_plan/release_readiness_checklist_v1.2.md

This page is the operational checklist for current release execution.