Release Checklist DIGIT Core 2.9
- Shashwat Mishra
- Sathish P
@Sl No | Checklist | Yes/No/Partially | Reference link | Owner | Reviewer | Remarks |
1 | Development is completed for all the features that are part of the release. | Yes | @Shashwat Mishra | @Aniket Talele | Code is frozen by 30-March-2023 | |
2 | Test cases are documented by the QA team and test results are updated in the test cases sheet. | Yes | @ShraddhaSolkar | @Aniket Talele |
| |
3 | The incremental demo of the features showcased during tech council meetings and feedback incorporated. | Yes |
| @Shashwat Mishra | @Ghanshyam Rawat @Aniket Talele |
|
4 | QA signoff is completed by the QA team and communicated to the platform team. All the tickets QA signoff status is updated in the JIRA. | Yes |
| @ShraddhaSolkar | @Aniket Talele @Shashwat Mishra | QA signoff was completed. 6th Feb 2023
|
5 | API Technical documents are updated for the release along with the configuration documents. | Yes | @Shashwat Mishra | @Aniket Talele |
| |
6 | UAT promotion and regression testing from the QA team is completed. | Yes | @ShraddhaSolkar | @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 |
| @ShraddhaSolkar |
| 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 |
| @ShraddhaSolkar | @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 |
| @ShraddhaSolkar | @Aniket Talele @Shashwat Mishra | UAT sign-off was completed on 24th March 2023
|
10 | UAT signoff communication is received from the Platform team along with the release notes and User guides (if applicable). | Yes |
| @ShraddhaSolkar | @Aniket Talele @Shashwat Mishra | All modules are signed off, release notes and user guides are updates
|
11 | The GIT tags and releases are created for the code changes for the release. | Yes | @Shashwat Mishra | @Aniket Talele |
| |
12 | Verify whether the Release notes are updated | Yes | @Shashwat Mishra @Anjoo Narayan | @Aniket Talele |
| |
13 | Verify whether all UAT Builds are updated along with the GIT tag details. | Yes | @Shashwat Mishra | @Aniket Talele |
| |
14 | Verify whether all MDMS, Configs, InfraOps configs updated. | Yes | @ShraddhaSolkar | @Shashwat Mishra |
| |
15 | Verify whether all docs will be Published to Introducing DIGIT Platform by the Technical Writer as part of the release. | Yes |
| @Shashwat Mishra
| @Anjoo Narayan |
|
16 | 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 | @ShraddhaSolkar | @Aniket Talele @Shashwat Mishra |
| |
17 | Verify whether the UAT credentials sheet is updated with the details of new Users and Roles if any | Yes |
| @ShraddhaSolkar | @Shashwat Mishra | UAT credentials shared internally to platform team |
18 | Verify whether all the localisation data was added in UAT including Hindi and updated in Release Kits. | Yes | @ShraddhaSolkar | @Shashwat Mishra |
| |
19 | 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. | |
20 | The Demo of technical enhancements is done by the platform team as part of the tech council meetings. | Yes |
| Platform team | @Ghanshyam Rawat @Aniket Talele @Shashwat Mishra |
|
21 | Technical and Product workshops/demos are conducted by the Engineering and Product team to the implementation team (Implementation handover) | NA |
|
|
|
|
22 | Architect SignOff and Technical Quality Report | Yes |
| @Ghanshyam Rawat @Aniket Talele |
| Sign off is given. |
23 | Success Metrics and Product Roadmap | NA |
|
|
|
|
24 | Adoption Metrics | NA |
|
|
|
|
25 | Program Roll-out Plan | NA |
|
|
|
|
26 | Implementation checklist | NA |
|
|
|
|
27 | Implementation Roll-out plan | NA |
|
|
|
|
28 | Gate 2 | Inprogress |
|
|
| planned on 20th-Feb-2023 |
29 | The Internal release communication along with all the release artefacts are shared by the Platform team. | Inprogress | @Shashwat Mishra | @Aniket Talele |
| After Gate 2 communication will be released |
30 | Plan for upgrading the staging/demo instance with the release product - within 2-4 weeks based on the period where no demos are planned from staging for the previous version of the released product. | No |
| @Pradeep Kumar |
| We don’t have clarity so as to when staging/demo instance is going to be upgraded to 2.9 |
31 | The Release communication to partners is shared by the GTM team and the Webinar is arranged by the GTM team after the release communication - within 2-4 weeks of the release. | NA |
|
|
|
|