Task | Status | Date | Reference/Comments |
|---|---|---|---|
Dev/Dev Lead Sachin S P , G S Prakash | |||
Ensure that all open pull requests (PRs) in the current release branch are reviewed and merged. | Done | Sep 4, 2024 | |
Code freeze in effect for the release branch, created from the develop branch. No further code changes until release completion. | Done | Sep 4, 2024 | <Link> |
Update Artifactory with required artifact versions for scheduled releases. | Done | ||
Review POM files: check main version and dependencies, remove SNAPSHOT references for non-release dependencies. | Done | Sep 4, 2024 | |
Platform Releases\Major Releases:
Component Release\Minor Releases:
| Done | Sep 4, 2024 | |
DB scripts and upgrade script are ready. File names must include correct SQL 'From' and 'To' versions. | NA | Sep 4, 2024 | |
If table structure or schema is changed, update the same for data archival. | NA | Sep 4, 2024 | |
Inform DevSecOps team for any change in the deployment script and make sure the script is updated before the sprint handover | NA | NA | |
Confirm default values in configuration files on the release branch. | NA | Sep 4, 2024 | |
Confirm debug log is disabled. | Done | ||
Update Annexure-1 (Repos & Sonar). | Done | Sonar - not in scope | |
Update Annexure-2. (POM version). | Done | ||
DSD for movement to QA environment. | NA | shared apk build pointing to qa env | |
Check all the internal dependency library versions in the POM file and compare with the latest release confluence page and update with the latest release version. If not done for any reason, jutify in the comments section for a each library. | NA | No change in internal dependency | |
Architect Vishwanath V update by Hitesh Champalal | |||
Define high-level architecture to guide development. | Done | Same as desktop for now. During stable release we will update. | |
Conduct a thorough review of the default values for all configuration changes, encompassing properties, JSON files in the config server, templates, policies, default DML, and other relevant settings to ensure accuracy and consistency. | NA | The default config from desktop reg client is used here | |
Review Artifactory (e.g. i18, All dependent Jar version, plugins, ICU4J, HSM client, etc). | NA | no runtime plugins are loaded from artifactory | |
Confirm DB upgrade script is added, verified, and properly named with correct 'Trom' and 'To' versions. | NA | No DB change in any server side components | |
Review critical code and confirm compliance with MOSIP standards. | Done | ||
Review API docs in Stoplight, ensure detailed field-level descriptions, and export to repository document folder. | NA | No API change | |
Check all the config change (new or old) for the correctness of values compared to the previously release version. | NA | No additional config changes | |
Verify Annexure-1. (repo list for the release). | |||
PO Pragya | |||
Release story is fully documented, complete, and closed. | Done | 4th September | |
Pending bugs, tasks, & stories are isolated and prioritized. | Done | 4th September | |
Country/ Real Device bugs reported bugs are listed and triaged. | NA | ||
All tasks' 'fix version' matches the release number. | Done | 4th September | |
Personally verified end-to-end functionality, ensuring it meets requirements. | Done | 4th September | |
JQL for all tickets going in the release referring to the release number field. | Done | 4th September | parent=RCF-31 and "Release Number[Labels]"=rcf-0.11.0 |
Documentation link for QA review. | Done | 4th September | |
Completion and verification of the functional documentation. | Done | 4th September | |
Release dashboard link. | Done | ||
Release planner link. | Done | Query: parent=RCF-31 and "Release Number[Labels]"=rcf-0.11.0 | |
Jira link for Security Bugs. | Done | ||
Request the Performance team for the final run and share report. (Dev team have completed the run and fine tuning before requesting performance team to provide the full run report for release) | NA | NA | Out of Scope |
Initiate request to DevOps for release deployment check. | Done |
| |
Initiate request for Test Automation to align with release. | Done |
| |
Update Annexure-3 (Test Automation Results). | Done |
| |
DevOps Rakshitha M | |||
Check deployability and assure no manual steps are involved. | NA | ||
Proper deployment documentation for the module is reviewed and verified for the specified release. | NA | ||
Deployment testing is performed following the deployment documentation. This can be a pair testing along with DevOps team member. Start on this post DevOps checks are completed. Till the deployment is stabilised, any issues, qa will cowork with devops team to avoid delays in the release. (time based provision till 30-Sep-24). | NA | ||
QA acceptance for the final release testing. | Yes | 29th Aug 2024 | |
Security Mahesh Binayak | |||
Security testing scope and approach was reviewed & approved by Architech. | NA | Testing is done and also received report. Bug fixing is in progress. Plan for next release. | |
Assure that the following standard security checks are performed:
| NA | ||
All scan reports are published in secure security confluence page. | NA | ||
Check the need for 3rd party security testing. | NA | ||
Confirm completion of security testing and provide open and closed bugs. | NA | <Open bugs link> <Closed bugs link> | |
...
Repo Name | Repo Owner | Base Branch Name (branch was created from which base branch) | Branch Name (getting released from this branch) | Order to build | Release Version (POM) (tag version is same as release version with prefix as 'v') | Dependent runtime Artifacts with version | Coverage (>80%) | Reliability (0) | Security (0) | Hotspots (0) | Duplications (Less than 3%) | Date | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
develop | release-0.11.x | 1 | v0.11.0-beta.1 | NA | NA | NA |
| ||||||||||||||
...