The Go/No-go checklist delineates the criteria that must be satisfied for the project/ modules to be approved for release. It enables stakeholders to make informed decisions regarding the current status and progress of the release, as well as identify any gaps or missing items.
| Item | Details |
|---|---|
Also, separate pages for each stakeholder in the pre-release section needs to be updated before entering the summarized status below.
| Role | Status | Comments |
|---|---|---|
When the Final Consolidated Status for the release is Go, the release in done.
Date
<dd-mm-yy>
Attendees
<list of attendees in the meeting>
Module
<module name>
Release
<version number>
Release Type
Beta/ Developer/ Stable/ LTS
Architect
BA
Developer
Performance
Security
Documentation
DevOps
QA
PMO
Final Consolidated Status