Content

Checklist

Freeze Phase

• Inform developer of the freeze
• All relevant tickets are assigned to epics
• Create release instance using the released components
• 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)
• Update keys and translations in Lokalise
• update the server and server page Release: openIMIS

Alpha Phase

• Perform some basic testing / Developer tests
• Claim: create/review/process
• Registration: create/update family/insuree
• Enrolment: create policy and contribution
• Meta data: create/update location/product/user/role/pricelist/itemslist/servicelist
• 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

• Officially announce the start of User Acceptance Tests (UAT)
• Check that the release instance uses the latest modules
• Add user account on the QA server
• Assign test cases to test users
• Do User-Acceptance-Testing (UAT)

RC Phase

• 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

• Merge release branches with main
• Create release in GitHub, versioned according to Version management 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 Demo: openIMIS)
• Demo: openIMIS Instance and Wiki page are up to date
• Mark all tickets in release as “Done” or push to the next release
• Check that Installation Guide supports installation of the latest release
• Check and update wiki page on Release 2025-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 linked issues as an anonymous user
• “Highlights” of the release are written and coherent

• Check and update Sources Release 2025-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, 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.

• Sandbox Landscape Other instances are up to date / compatible with Demo: openIMIS / Release: openIMIS
• Ensure the documentation is up2date
• User Documentation openIMIS User Manual (EN) / Application Web openIMIS (modes d'emploi)
• 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 2025-04 ) in Jira and add them to the release page
• Create the release page (e.g. Release 2025-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 2025-04 )