...
- 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 and Country LocalisationGuide 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 similar repositories / package manager
- Formulate release notes in current release (Releases) and forward it to co-ordination desk for promotion (e.g. newsletter, Twitter)
- Wikipedia page refers to the latest release (number)
Post-Release
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 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 guideGuide reflects latest release
- “Technical Requirements” / Connectivity & theoretical infrastructure required reflects latest release
- Sandbox Landscape Other instances are up to date / compatible with Demo: openIMIS / Release: openIMIS
...