/
Checklist for Release 2026-04

Checklist for Release 2026-04

Content

Checklist

Freeze Phase

Inform developer of the freeze
Create the release epic in Jira https://openimis.atlassian.net/browse/OP-2792
All relevant tickets (from the previous release) are assigned to epics (search status = "To be released" and parent= EMPTY)
Make sure that the development server works properly
Check the Continuous Integration in very fine details (read through the logs)
Create the release branches (gh-create-release-branch.py) (additional bugfixing PRs can still be added later)
Create the openimis.json (gh-make-release-openimis-json.py) and load result in the release assembly branches
Create the release docker image
commit created openimis.json to respective repos
Update .env with the new release image TAG and run docker compose pull && docker compose up -d --remove-orphans
Apply migrations using docker compose exec backend python manage.py migrate
Inform the implementers about the User Acceptance Test (UAT) timeline (Beta version)
Create the release on TestLink (QA server) https://qa.openimis.org
Update keys and translations in Lokalise and update language packs
Update the release server (deploy)
In parallel: update server page Release: openIMIS

Alpha Phase

Run scripts for synthetitic data
fake_individuals
generate_synthetic_data
Perform some basic testing on release server ( developer tests )
Claim: create/review/process
Registration: create/update family/insuree
Enrolment: create policy and contribution
Meta data / Admin :-
location
product
user
role
pricelist
itemslist
servicelist
cash-transfer: …/…/…
Make sure defects were fixed by developers
Release: openIMIS Instance and Wiki page are up to date
Make freeze on documentation on the wiki https://openimis.atlassian.net/wiki/spaces/KB

Beta Phase

Pre-Formulate release notes in current release (Releases) and forward it to co-ordination desk for promotion (e.g. mailing list, LinkedIn)
Officially announce the start of User Acceptance Tests (UAT)
after 2 to 3 days announce it on linkedin
Check that the release instance uses the latest modules (github actions / docker compose pull)
Add user accounts for new users on the testlink server (https://qa.openimis.org/login.php )
Assign test cases to test users
Do User-Acceptance-Testing (UAT)

RC Phase

Fix all the issues from the UAT (update: most fixed/cancelled)
Ensure deployability with Docker (Quickstart installation guide / Docker compose)
Check that the release instance use the latest modules
Start collecting the documentation from developers

GA Phase

Create releases in GitHub,
Run script (gh-make-release.py) to publish modules automatically (on PyPi and NPM) and bump version numbers according to https://openimis.atlassian.net/wiki/spaces/OP/pages/290455555
Update the openimis.json in assemblies (backend and frontend) main branch to use only official version (not RC) (gh-make-release-openimis-json.py)
create final release image (using pip/npm packages), check the log to ensure all package are published
Create github release release-notices for each of the changed repositories (don’t forget )
Update demo server
indicate maintenance status on Demo: openIMIS
pull images, restart docker
Demo: openIMIS Instance and Wiki page are up to date
Mark all jira-tickets in release as “Done” or push to the next release
Merge all release branches to develop (gh-pr-release-to-develop.py)
Check that Installation Guide supports installation of the latest release
Check and update wiki page on Release 2026-04
All links on the release page and release sources page are working and are helpful; Dates are correct and the status is “GA”
Analyze links as an anonymous user
“Highlights” & “Attention Points” of the release are written and coherent
Check and update Sources Release 2026-04
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 (Releases) and forward it to co-ordination desk for promotion (e.g. newsletter, LinkedIn)
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.

Sandbox Landscape Other instances are up to date / compatible with Demo: openIMIS / Release: openIMIS
Ensure the documentation is up2date
Tutorials on YouTube are up-to-date / not misleading
Developer Starter Kit reflects latest release
Installation Guide reflects latest release
“Technical Requirements” / Connectivity & theoretical infrastructure required reflects latest release
Prepare the next release
Create the relevant epics for the new release (e.g. Release 2026-04 ) in Jira and add them to the release page
Create the release page (e.g. Release 2026-04 ) for the following release and make sure it appears correctly on Releases
Define milestones according to the framework in Releases
Create a clean Release Checklist for the next release (e.g. Release 2026-04 )

 

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/