Checklist
Pre-Release
Start release planning immediately after each release according to the section Post-Release below - maybe there is actually not pre-release phase - to be verified
| Table of Contents | ||||
|---|---|---|---|---|
|
Checklist
Freeze Phase
- Create the release on the QA server
- Inform developer of the freeze
- Create the release branches
- Define the version of the modules based on semantic versioning
- All relevant tickets are assigned to epics
- Check the Continuous Integration in details
- Inform the implementers about the User Acceptance Test (UAT) timeline (Beta version)
- Add user account on the QA server
...
- Create release instance using the released modules
- 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 are assigned to developers
- Do developer tests
- were fixed by developers
- Release: openIMIS Instance and Wiki page are up to date
Beta Phase
- Update the PyPi, NPM module when code change was done
- Check that the release instance use the latest modules
- Do User-Acceptance-Testing (UAT)
- Ensure deployability with Docker (Quickstart installation guide / Docker compose)
...
- 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.jsonin assemblies main branch to use only official version (not rcRC) - 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 / Installation and Country Localisation supports installation of the latest release
- Check and update Release 2022-10
...
- Check and update Sources Release 2022-04
- All source components link to the correct repository on GitHub, have the correct version, valid release notes and are reasonably named to similiar similar repositories / package manager
- Formulate release notes in current release (Releases) and forward it to co-ordination desk for promotion (e.g. newsletter, Twitter)
...
Start preparing the next release immediately after the current release.
- Create the relevant epics for the new release (e.g. Release 2022-10 ) in Jira and add them to the release page
- Create the release page (e.g. Release 2022-10 ) for the following release and make sure it appears correctly on Releases
- Define milestones according to the framework in Releases
- Create the relevant epics for the new release (e.g. Release 2022-10 ) in Jira and add them to the release pageCreate a clean Release Checklist for the next release (e.g. Release 2022-10)
- Ensure the documentation is up2date
- User Documentation http://docs.openimis.org/en/latest/ / http://docs.openimis.org/fr/latest/
- Tutorials on YouTube are up-to-date / not misleading
- Developer Starter Kit reflects latest release
- Installation guide reflects latest release
Following need to be integrated
Installation Guide / Configuration / Other
- “Technical Requirements” / Connectivity & theoretical infrastructure required reflects latest release
Sandbox Landscape Sandbox Landscape
- Demo: openIMIS Instance and Wiki page are up to date
- Release: openIMIS Instance and Wiki page are up to date
- Sandbox Landscape Other instances are up to date / compatible with Demo: openIMIS / Release: openIMIS
...