Release Checklist
| Sl.No. | Checklist | Yes/No/Partially | Reference Link | Owner | Reviewer | Remarks |
|---|---|---|---|---|---|---|
1 | Upgrade is completed for all the core services that are part of the release. | Yes | NA | Shashwat Mishra | Code is frozen by 14 March 2024 | |
2 | Test cases are documented by the QA team and test results are updated in the test cases sheet. | Yes | Mustakim | |||
3 | The incremental demo of the features showcased during tech council meetings and feedback incorporated. | Yes | NA | Shashwat Mishra | ||
4 | QA signoff is completed by the QA team and communicated to the platform team. | Yes | NA | QA signoff was completed. Sign-off dates 6th Feb 2023 | ||
5 | API Technical documents are updated for the release along with the configuration documents. | Yes | NA | |||
6 | Promotion to new environment testing from the QA team is completed. | Yes | NA | Shraddha Solkar | Aniket Talele Shashwat Mishra | |
7 | API Automation scripts are updated for new APIs or changes to any existing APIs for the release. API automation regression is completed on UAT, the automation test results are analyzed and necessary actions are taken to fix the failure cases. Publish the list of failure use cases with a reason for failure and the resolution taken to fix these failures for the release. | No | NA | Shraddha Solkar | Not picked up in this release due to lack of resources. We do not have QA resource who can write automation scripts. | |
8 | The API backward compatibility testing is completed. | Yes | Shraddha Solkar | Aniket Talele Shashwat Mishra | Core modules were tested against urban 2.8 modules and the bugs which were found have been addressed. | |
9 | The communication is shared with the platform team for regression by the QA team. | Yes | NA | Shraddha Solkar | Aniket Talele Shashwat Mishra | UAT sign-off was completed on 24th March 2023 |
10 | The GIT tags and releases are created for the code changes for the release. | Yes | Shashwat Mishra | Aniket Talele | ||
11 | Verify whether the Release notes are updated | Yes | Shashwat Mishra Anjoo Narayan | Aniket Talele | ||
12 | Verify whether all MDMS, Configs, InfraOps configs updated. | Yes | NA | Shraddha Solkar | Shashwat Mishra | |
13 | Verify whether all docs will be Published to Introducing DIGIT Platform by the Technical Writer as part of the release. | Yes | NA | Shashwat Mishra | Anjoo Narayan | |
14 | Verify whether all test cases are up to date and updated along with necessary permissions to view the test cases sheet. The test cases sheet is verified by the Test Lead. | Yes | Shraddha Solkar | Aniket Talele Shashwat Mishra | ||
15 | Verify whether all the localisation data was updated in Release Kits. | Yes | Shraddha Solkar | Shashwat Mishra | ||
16 | Verify whether the platform release notes and user guides are updated and published | Yes | Platform team | Aniket Talele Shashwat Mishra | Release notes and user guides are published in gitbook. | |
17 | The Demo of technical enhancements is done by the platform team as part of the tech council meetings. | Yes | NA | Platform team | Ghanshyam Rawat Aniket Talele Shashwat Mishra | |
18 | Architect SignOff and Technical Quality Report | Yes | NA | Ghanshyam Rawat Aniket Talele | Sign off is given. | |
19 | The release communication along with all the release artefacts are shared by the Platform team. | Inprogress | NA | Shashwat Mishra | Aniket Talele |
Last updated