> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v2.0/introducing-public-health/release-notes/release-checklist.md). # Release Checklist


Checklist	Yes/No/Partially	Reference Link/ETA	Owner	Reviewer	Remarks
The development is complete for all the features that are part of the release.	Yes		Jagankumar Naveen J	Kaviyarasan P
Test cases are documented by the QA team, reviewed by product owners, and test results are updated in the test cases sheet.	Yes		Lata Naik Shreya Kumar	@Sruthi
The incremental demo of the features showcased during the sprint showcase and feedback is incorporated. If possible, list out the JIRA tickets for feedback.	Yes		Shreya Kumar Lata Naik	Jagankumar Naveen J
UI/UX audit review is completed along with feedback incorporation for any changes in UI/UX.	Yes		Jagankumar Naveen J	Andrew Jones
QA sign-off is completed by the QA team and communicated to product owners. All the tickets’ QA sign-off status is updated in JIRA.	Yes		Lata Naik Shreya Kumar	Kaviyarasan P
UI, and API technical documents are updated for the release along with the configuration documents.	Yes		Jagankumar Naveen J
UAT promotion and regression testing from the QA team is completed. The QA team has shared the UAT regression test cases with the product owners.	Yes	Regression Test Cases	Lata Naik Shreya Kumar
The API backward compatibility testing is completed.	Yes		Lata Naik	Kaviyarasan	Ongoing Testing
The communication is shared with product owners for the completion of UAT promotion and regression by the QA team. The product owners have to give a product sign-off within one week of this communication.	Yes		Lata Naik Shreya Kumar
The UAT product sign-off communication is received from product owners along with the release notes and user guides (if applicable).	Yes		@Akhil @Anshumanth	Ranjani Rajagopalan
The GIT tags and releases are created for the code changes for the release.	Yes		Jagankumar Naveen J	Kaviyarasan P
Verify whether the release notes are updated.	Yes		Jagankumar Naveen J
Verify whether all the UAT builds are updated along with the GIT tag details.	Yes		Lata Naik Shreya Kumar	Jagankumar Naveen J
Verify whether all MDMS, configurations, infra-ops configurations are updated.	Yes	Release tag, API Postman	Lata Naik Shreya Kumar	Jagankumar Naveen J
Verify whether all docs will be published to http://health.digit.org by the Technical Writer as part of the release.	Partially		@Anjoo
Verify whether all test cases are up-to-date and updated along with the necessary permissions to view the test cases sheet. The test cases sheet is verified by the test lead.	Yes		Lata Naik Shreya Kumar	@Sruthi
Verify whether the UAT credentials' sheet is updated with the details of new users and roles, if any.	Yes	User Credentials	Lata Naik Shreya Kumar	@Akhil @Anshumanth
Verify whether all the localisation data was added in UAT, and updated in the release kits.	Yes		Lata Naik Shreya Kumar		No functional changes were made
Verify whether the product release notes and user guides are updated and published.	Yes		@Akhil @Anshumanth		No product functional changes were made
The demo of the released features is done by the product team as part of a sprint/release showcase.	Yes		Jagankumar Naveen J	@Akhil	Several Demos have been given to Solutions team and PO for all Projects of HCM v1.6
Technical and product workshops/demos are conducted by the engineering and product teams respectively to the implementation team (implementation handover).	Yes		Jagankumar Naveen J	Ankit Sharma	Several Demos have been given to Solutions team and PO for all Projects of HCM v1.6
Architect sign-off and technical quality report.	Yes		Jagankumar Naveen J	Kaviyarasan P
Verify Bug Bash has been completed	Yes		Jagankumar Naveen J	@Akhil @Anshumanth
Gate 2	Yes				16th Dec
The internal release communication along with all the release artefacts are shared by the engineering/ product teams.	Yes

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.digit.org/health/v2.0/introducing-public-health/release-notes/release-checklist.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.