Overview

Overview

When to Create a Release Note

Create a release note for every production release, including hotfix releases.

The release note should be created before rollout starts and updated during QA execution.

Source of Truth

• Template: Release Note Template
• Convention: Release Notes Convention
• Storage: Release Notes Folder

QA Execution Model

1. Read the release summary and risk snapshot.
2. Execute all Critical checks first.
3. Execute High and Medium checks in order.
4. Re-validate listed unaffected critical flows.
5. Record evidence and final result for every check.
6. Complete QA signoff and hand back to Engineering signoff.

Required Fields for Signoff

• Engineering owner
• QA owner
• Release date
• Final QA decision (Pass, Pass with risk, or Blocked)

Definition of Done

A release note is complete when:

• all required sections are filled,
• every check has a result,
• blockers (if any) are clearly documented,
• and QA plus Engineering signoff are captured.