Checklist for Release 2022-10

Content

Checklist

Freeze Phase

Inform developer of the freeze
All relevant tickets are assigned to epics
Create release instance using the released components
Define the version number of the modules based on semantic versioning
Create the release branches
Check the Continuous Integration in details
Inform the implementers about the User Acceptance Test (UAT) timeline (Beta version)
Create the release on TestLink (QA server)

Alpha Phase

Perform some basic testing / Developer tests
Claim: create/review/process
Registration: create/update familly/insuree
Enrollment: create policy and contribution
Meta data: create/update location/product/user/role/pricelist/itemslist/servicelist
Make sure defects were fixed by developers
https://openimis.atlassian.net/wiki/spaces/OP/pages/3220930578 Instance and Wiki page are up to date

Beta Phase

Officially announce the start of User Acceptance Tests (UAT)
Check that the release instance use the latest modules
Do User-Acceptance-Testing (UAT)
Add user account on the QA server

RC Phase

Ensure deployability with Docker (Quickstart installation guide / Docker compose)
Update the PyPi, NPM module when code change was done
Check that the release instance use the latest modules
Start collecting the documentation from developers

GA Phase

Merge release branches with main
Create release in GitHub, versioned according to https://openimis.atlassian.net/wiki/spaces/OP/pages/290455555 and containing complete release notes (should publish automatically the release on PyPi and NPM)
Update the openimis.json in assemblies main branch to use only official version (not RC)
Update demo server (mark maintenance window on https://openimis.atlassian.net/wiki/spaces/OP/pages/3221225480)
Mark all tickets in release as “Done” or push to the next release
Check that https://openimis.atlassian.net/wiki/spaces/OP/pages/786104344 supports installation of the latest release
All links on the release page and release sources page are working and are helpful; Dates are correct and the status is “GA”
Analyze linked issues as an anonymous user
“Highlights” of the release are written and coherent
All source components link to the correct repository on GitHub, have the correct version, valid release notes and are reasonably named to similar repositories / package manager
Formulate release notes in current release (https://openimis.atlassian.net/wiki/spaces/OP/pages/1322221610) and forward it to co-ordination desk for promotion (e.g. newsletter, Twitter)
Check and update the Wikipedia page, that it refers to the latest release (number) and reflects the technical facts of openIMIS correctly

Post-Release

Start preparing the next release immediately after the current release.

Ensure the documentation is up2date
Tutorials on YouTube are up-to-date / not misleading
“Technical Requirements” / https://openimis.atlassian.net/wiki/spaces/OP/pages/898924553 reflects latest release
Prepare the next release
Create the relevant epics for the new release (e.g. https://openimis.atlassian.net/wiki/spaces/OP/pages/3308093441 ) in Jira and add them to the release page
Create the release page (e.g. https://openimis.atlassian.net/wiki/spaces/OP/pages/3308093441 ) for the following release and make sure it appears correctly on https://openimis.atlassian.net/wiki/spaces/OP/pages/1322221610
Define milestones according to the framework in https://openimis.atlassian.net/wiki/spaces/OP/pages/1322221610
Create a clean Release Checklist for the next release (e.g. https://openimis.atlassian.net/wiki/spaces/OP/pages/3308093441)

 

Did you encounter a problem or do you have a suggestion?

Please contact our Service Desk



This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. https://creativecommons.org/licenses/by-sa/4.0/