> 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/v1.5/introducing-health/release-notes/hcm-v1.4-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	Link	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	Link	Lata Naik	Pritish Rath
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	12-June-24	Kanishq Bhatnagar Naveen J
UI/UX audit review is completed along with feedback incorporation for any changes in UI/UX.	Yes	30-May-24	Naveen J	Andrew Jones	Mail has been communicated to Andrew Jones for UI/UX audit
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	Link	Lata	Kaviyarasan P
UI, and API technical documents are updated for the release along with the configuration documents.	Yes	Link	Ramkrishna Sahoo	Mihika Basu
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	Link	Lata	Abhishek Suresh
The API backward compatibility testing is completed.	Yes		Lata Naik	Kaviyarasan P	No breaking changes are made.
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	4-June 24	Lata Naik	Pritish Rath	As part of admin console product owner sign-off has been completed
The UAT product sign-off communication is received from product owners along with the release notes and user guides (if applicable).	Yes	20-June-24	Abhishek Suresh	Ranjani Rajagopalan	As part of admin console product owner sign-off has been completed
The GIT tags and releases are created for the code changes for the release.	Yes	Link	Kanishq Bhatnagar, Naveen J	Kaviyarasan P
Verify whether the release notes are updated.	Yes	Link	Naveen J Kaviyarasan P	Pritish Rath
Verify whether all the UAT builds are updated along with the GIT tag details.	Yes	Link	Lata	Kaviyarasan P
Verify whether all MDMS, configurations, infra-ops configurations are updated.	Yes	Release tag, API Postman	Kanishq Bhatnagar Ramkrishna Sahoo	Kaviyarasan P
Verify whether all docs will be published to http://health.digit.org by the Technical Writer as part of the release.	Partially		Mihika Basu
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	HCM v1.5 Test cases	Lata Naik	Pritish Rath
Verify whether the UAT credentials' sheet is updated with the details of new users and roles, if any.	Yes	Link	Lata Naik	Abhishek Suresh
Verify whether all the localisation data was added in UAT, and updated in the release kits.	Yes	Link	Lata Naik		No functional changes were made
Verify whether the product release notes and user guides are updated and published.	No		Abhishek Suresh		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	20-June-24	Naveen J Kaviyarasan P	Abhishek Suresh	Demo has been give as a part of the HCM Console release
Technical and product workshops/demos are conducted by the engineering and product teams respectively to the implementation team (implementation handover).	Yes		Naveen J Kaviyarasan P	Ankit Sharma
Architect sign-off and technical quality report.	Yes		Kaviyarasan P	Kaviyarasan P
Verify Bug Bash has been completed	Yes	31-May-24	Lata Naik	Pritish Rath
Gate 2		21-Jun-24
The internal release communication along with all the release artefacts are shared by the engineering/ product teams.

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digit.org/health/v1.5/introducing-health/release-notes/hcm-v1.4-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 what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.