/
ARC 0.10.0 Developer Pre-release Checklist

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 : , , , , ,

Tasks

Status

Completed date

Comments

Get architect approval on design and develop code for all release repo

Done

13-06-2024


Tasks for the release are detailed, completed and closed

Done

13-06-2024


Branching out of the feature branch to the release branch

Done

13-06-2024


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

Done

13-06-2024


DB scripts and upgrade script is written and verified. Make sure proper SQL From and To version is maintained in naming of the file.

Done

13-06-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

Yes

13-06-2024


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

Yes

13-06-2024


Absolute code freeze including bug fix

Yes

13-06-2024


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

Yes

13-06-2024


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

Yes

13-06-2024


Release branch and develop branch code base are in sync

Yes

13-06-2024


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

Yes

13-06-2024


Developer documentation in github is available (.md file)

Yes

13-06-2024


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




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

Yes

13-06-2024


Provide development architecture to documentation team

Yes

Jun 13, 2024


Provide technical documentation to documentation team

Yes

Jun 13, 2024


Release notes prepared by BA is reviewed by developer

Yes

13-06-2024


Check deployability and assure no manual steps involved

Yes

13-06-2024


Version compatibility matrix

Yes

13-06-2024


Repos going in the release consolidated status and approved by Architect

Yes

13-06-2024


Sonar consolidated status

Yes

13-06-2024


Anchor
​ 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

android-registration-client

Public

release-0.9.x

0.10.0

0.10.0




















Note: Sonar Coverage above 80%, code duplications < 3%, Reliability, Security and Hotspot should be 0

Legend

Anchor
Tasks:

  • The list of tasks against which the status needs to be updated. Since it’s a template, go ahead to add/modify as required

Anchor
Status:

  • 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

Anchor
Status Date:

  • Enter the date when the Status was provided for a given stream

Anchor
Comments:

  • Enter the comments as relevant for a given stream

Anchor
Repo Name:

  • Name of the repository available in version control system. (Github)

Anchor
Module Dependency:

  • Enter the name of the module which is dependent for the given repo

Anchor
Service/Library:

  • Name of the artifact from the module dependency

Anchor
:Dependency Type & Version

  • Name of the artifact from the module dependency and it’s version

Type of dependency(Direct/Indirect)


Anchor
POM Version

  • Make sure that dependent POM version are correctly updated for the service/library