Lead developer of the project to ensure all the below checklist tasks are performed and the status is updated before the Go/NoGo release call.
Owner : @Piyush Shukla , @Aviral Mishra , @Aditya Singh , @G S Prakash , @Sachin S P , @Himaja Dhanyamraju
Tasks | Status | Completed date | Comments |
|---|---|---|---|
Get architect approval on design and develop code for all release repo | Go | 21-02-2024 | Design and develop code was approved by Hitesh and Anusha. |
Tasks for the release are detailed, completed and closed | Go | 21-02-2024 | Tasks are completed and closed. |
Branching out of the feature branch to the release branch | Go | 21-02-2024 | Release code is available on release branch. |
Move the finalized design/approach of all the new features from confluence page to repository doc folder | Go | docs.mosip.io | |
DB scripts and upgrade script is written and verified. Make sure proper SQL From and To version is maintained in naming of the file. | NA | 21-02-2024 | |
All the API docs in stoplight should have detailed descriptions till the fields level and same need to be exported and moved into the docs folder of the repositories (not to commit in develop branch) | NA | ||
Export a copy of the Open API docs from stoplight and keep it under the docs folder of the repo | NA | ||
Make sure that configuration has the default values as per the release requirements are in release branch | Go | 21-02-2024 | All configurations have default values as per release requirements. |
Sample Country-specific data and also document the way of inserting/updating them in the database mostly via REST endpoints provided? e.g. format Database | Table | Sample Data | Module | Module Version | Details | Comments | NA | 21-02-2024 | |
Absolute code freeze including bug fix | Go | ||
No open PR in the develop repo for all modules about to get released | Go | 21-02-2024 | Develop has no open PR. |
Dependencies not part of the release list should not have SNAPSHOT references | Go | 21-02-2024 | |
Release branch and develop branch code base are in sync | Go | ||
Dependencies of repo and the order in which repos should be built is verified | Go | 21-02-2024 | Verified |
Developer documentation in github is available (.md file) | Go | ||
Postman collection is tested by QA, available in the release branch | NA | 21-02-2024 | |
Review commits from earlier release version in the current release to be checked | Go | ||
Provide development architecture to documentation team | Go | 21-02-2024 | All specifications are with documentation team. |
Provide technical documentation to documentation team | Go | 21-02-2024 | All specifications are with documentation team. |
Release notes prepared by BA is reviewed by developer | Go | ||
Check deployability and assure no manual steps involved | Go | ||
Version compatibility matrix | Go | 21-02-2024 | Version compatibility is fine. |
Repos going in the release consolidated status and approved by Architect | Go | 21-02-2024 | |
Sonar consolidated status | NA | 21-02-2024 | Flutter has a limitation with Sonar. |
Before filling this section, make sure that code is already merged out to release-xxxx branch
Repo Name | Repo Owner | Branch Name | Release Version (POM) | Tag Version | Coverage (>80%) | Reliability (0) | Security (0) | Hotspots (0) | Duplications (Less than 3%) | Data capture date | Comments |
|---|---|---|---|---|---|---|---|---|---|---|---|
Note: Sonar Coverage above 80%, code duplications < 3%, Reliability, Security and Hotspot should be 0
Legend
The list of tasks against which the status needs to be updated. Since it’s a template, go ahead to add/modify as required
Go - Go ahead from the stake holder to release for a given stream
NoGo - Stake holder does not want the release to go for a given stream
In-progress - Work is in progress to provide final decision for a given stream
NA - Specific part of section is not applicable for this release for a given stream
Enter the date when the Status was provided for a given stream
Enter the comments as relevant for a given stream
Name of the repository available in version control system. (Github)
Enter the name of the module which is dependent for the given repo
Name of the artifact from the module dependency
Name of the artifact from the module dependency and it’s version
Type of dependency(Direct/Indirect)
Make sure that dependent POM version are correctly updated for the service/library