# Go/No Go Release Checklist

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.

<table><thead><tr><th width="170">Item</th><th>Details</th></tr></thead><tbody><tr><td>Date</td><td>&#x3C;dd-mm-yy></td></tr><tr><td>Attendees</td><td>&#x3C;list of attendees in the meeting></td></tr><tr><td>Module</td><td>&#x3C;module name></td></tr><tr><td>Release</td><td>&#x3C;version number></td></tr><tr><td>Release Type</td><td>Beta/ Developer/ Stable/ LTS</td></tr></tbody></table>

Also, separate pages for each stakeholder in the pre-release section needs to be updated before entering the summarized status below.

| Role                          | Status | Comments |
| ----------------------------- | ------ | -------- |
| Architect                     |        |          |
| BA                            |        |          |
| Developer                     |        |          |
| Performance                   |        |          |
| Security                      |        |          |
| Documentation                 |        |          |
| DevOps                        |        |          |
| QA                            |        |          |
| PMO                           |        |          |
| **Final Consolidated Status** |        |          |

When the Final Consolidated Status for the release is <mark style="color:green;">**Go,**</mark> the release in done.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mosip.io/1.2.0/community/code-contributions/release-process/go-nogo.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.