Pre-release Check for Go/NoGo

Dev/Dev Lead @Sachin S P , @G S Prakash

API docs in Stoplight for detailed descriptions upto the fields level and the same is exported and moved into the document folder of the repositories.

NA

Sep 4, 2024

No APi changes

Developer readme documentation in github is available (.md file).

Yes

Sep 4, 2024

Move the finalized design / approach of all the new features from confluence page to repository doc folder.

NA

Sep 4, 2024

https://mosip.atlassian.net/browse/RCF-972

Provide development architecture to documentation team.

Yes

Sep 4, 2024

Provide technical documentation to documentation team.

Yes

Sep 4, 2024

Update Annexure-1 (Version compatibility matrix)

Location form where the configuration (properties, JSON and any other files in mosip-config) file names to be referred to.

<[GitHub links here]>

Review commits from earlier release version in the current release to be checked.

Architect @Hitesh Champalal

Review technical documentation for the release (e.g. design documentation, developer guide, readme, dependency matrix).

Yes

Security testing approach is reviewed. Open bugs are to be reviewed and confirm if it’s okay to release with open bugs.

Yes

there are known issues related to signing which implementor can mitigate with their keys

Review all the API docs in stoplight for detailed descriptions upto the fields level and the same is exported and moved into the document folder of the repositories.

NA

PO/BA @Pragya

Release notes is prepared and got reviewed from the following tracks:

1. Dev/DevLead, QA, Test Automation, Performance, Security, DevOps.

https://mosip.atlassian.net/wiki/spaces/PM/pages/1075216434

Done

Release Notes

Inform relevant stake holders about the upcoming release.

Done

Identify the Sample Country-specific data. Also, document the way of inserting / updating them in the database (mostly via REST endpoints provided.). If there is any script prepared for the same, it should also be released, and there should be a documentation on how to use it.

e.g. format Database | Table | Sample Data | Module | Module Version | Details | Comments

Done

Known bugs are mentioned in the release notes.

Done

parent=rcf-31 and issuetype=bug and status not in (closed, Canceled) and labels!=ARC_Real_Device

Breaking changes or incompatible versions are mentioned in the release notes.

Done

KT Videos completed.

Open

QA @Maheswara Sarma

Postman collection is tested by QA, available in the release branch.

NA

Mechanism for QA to verify the version (library that is present in the artifactory).

NA 

Release version testing against docker, artifacts, branch, env, etc. is documented and included in the test report.

 Yes

 4th Sep 2024

Backward compatibility is tested.

NA 

Security Testing approach and outcome are reviewed including bugs

NA 

All testing artifacts are available in GitHub going for the release.

NA

 <Link>

Upgrade testing is performed.

NA 

Prometheus scraping is verified. (Kibana?)

Upgrade documentation is reviewed.

 NA

Functional documentation is reviewed (mosip docs).

Done

Completed

App available and verified from iOS Test Flight

 NA

Android apk available and verified from the confluence page.

 Done

 @Hitesh Champalal

Build from release-0.11.x branch

Docker compose testing is performed for Windows, Mac, Linux, Centos.

NA

Test Automation @jayesh kharode

Architect has reviewed the test automation code.

 NA

Branching out to the release branch is done.

NA

Automation tests are preparing runtime data required for execution.

NA

Automation tests are deleting test data generated after test execution.

NA 

Code freeze is done. DSD reference.

NA

 <Link>

Check there are no open PR in the release branch.

NA

Release branch and develop branch are in sync.

 NA

Dependencies not part of the release list should not have SNAPSHOT references.

NA

Documentation related requirement for settinng up, running, new enhancement, fixes, etc is completed.

NA

Update Annexure-2 (Test Automation Numbers). API Test automation run from the last tagged release.  This is to ensure that no existing API is changed in this release.  The result needs to be in line with the last released numbers.

NA

Documentation is updated for end user usage.

NA

Update Annexure-2 (Test Automation Numbers).

Done

Performance @Akhilesh Moogi

Performance scope reviewed by PO.

NA

Performance design, execution and environment is reviewed by Architect.

NA

Performance results are reviewed by DevLead and Architect.

NA

<Link perf result>

Performance tests scripts are reviewed by QA team.

NA

Confirm completion of performance testing and list open and closed bugs.

NA

<Open bugs link>

<Closed bugs link>

Documentation @vibha gondkar

Functional Documentation completed.

 Done

Sep 5, 2024

 Link

End user guide completed.

 Done

Sep 5, 2024

 Link

Standards/Specifications/ISO completed.

NA

Try it out (Collab).

NA

Build and Deployment documentation completed.

NA

Developer readme guide completed.

Done

Sep 5, 2024

 Link

Release notes prepared.

Done

Sep 5, 2024

https://docs.mosip.io/1.2.0/releases/android-registration-client-v0.11.0

DevOps @Rakshitha M

Deployment scripts are ready.

NA

Check deployability and assure no manual steps involved.

NA

PMO @HariKrishna Reddy

This checklist is upto date, verified and reviewed.

Done

Sep 5, 2024

Ready for Go/NoGo call.

Done

Sep 5, 2024