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 (Unlicensed) , 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

Tasks for the release are detailed, completed and closed

Go

Branching out of the feature branch to the release branch

Go

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

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

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)

Export a copy of the Open API docs from stoplight and keep it under the docs folder of the repo

Make sure that configuration has the default values as per the release requirements are in release branch

Go

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

Absolute code freeze including bug fix

No open PR in the develop repo for all modules about to get released

Go

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

Go

Release branch and develop branch code base are in sync

Dependencies of repo and the order in which repos should be built is verified

Go

Developer documentation in github is available (.md file)

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

NA

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

Provide development architecture to documentation team

Go

Provide technical documentation to documentation team

Go

Release notes prepared by BA is reviewed by developer

Check deployability and assure no manual steps involved

Version compatibility matrix

Go

Repos going in the release consolidated status and approved by Architect

Go

Sonar consolidated status

NA

Repos going for the release & Sonar detailed status for each repo to be released

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

Tasks:

Status:

Status Date:

Comments:

Repo Name:

Module Dependency:

Service/Library:

:Dependency Type & Version

Type of dependency(Direct/Indirect)

POM Version