...
- 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 2024-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
...
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 /wiki/spaces/SB/pages/3622502401 / https:/wiki/openimis.atlassian.net/wikispaces/SB/pages/createpage.action?spaceKey=SB&title=documentation%20openIMIS%20%28FR%293727130625
- 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 2024-04 ) in Jira and add them to the release page
- Create the release page (e.g. Release 2024-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 2024-04 )
...