Release Candidate Summary
Template Library
Release Candidate Summary
Identify the release candidate, baseline, commit, tag, release type, included/excluded capabilities, assumptions, and release question.
ES-110
Candidate
Release Identity
Template purpose
Use this template to identify the release candidate and the decision being made.
Project
<Project name>
Document control
| Field |
Value |
| Artifact owner |
<owner> |
| Primary reviewers |
<reviewers> |
| Status |
<draft / in review / accepted / revised> |
| Last updated |
<YYYY-MM-DD> |
| Related Engineering Stage |
ES-110 — Release Readiness |
| Project workspace target |
docs/project-workspace/release/release_candidate_summary.md |
Release candidate
| Field |
Value |
| Candidate ID |
<id> |
| Baseline / Commit / Tag |
<baseline> |
| Repository / Branch |
<repository / branch> |
| Release Type |
<production / limited pilot / internal demo / deferred> |
| Review Date |
<date> |
| Decision Owner |
<owner> |
| Intended Release Window |
<date / window / not applicable> |
| Related Testing Summary |
docs/project-workspace/testing/testing_readiness_summary.md |
Release question
<What decision is being made?>
Included capabilities
| Capability |
Source Requirement |
Evidence |
<capability> |
<FR/NFR/C-ID> |
<evidence> |
Excluded capabilities
| Capability |
Reason Excluded |
Communication Needed |
<capability> |
<reason> |
<yes / no / details> |
Candidate changes since last baseline
| Change |
Source |
Evidence |
<change> |
<work item / defect / requirement / risk> |
<evidence> |
Candidate assumptions
| Assumption |
Impact if Wrong |
Follow-up |
<assumption> |
<impact> |
<follow-up> |
Review checklist
- [ ] Candidate ID and baseline are clear.
- [ ] Release type is explicit.
- [ ] Included and excluded capabilities are listed.
- [ ] Release question is clear.
- [ ] Candidate links to testing evidence.
Continue to Release Scope
Proceed to the next ES-110 release readiness artifact.
Open Release Scope →