...
- Merge release branches with main
- All affected repositories (GitHub, Pypi.org, http://npmjs.com , etc.) are tagged and Create release in GitHub, versioned according to Version management and contain containing complete release notes on GitHub
- All source components link to the correct repository on GitHub, have the correct version, valid release notes and are reasonably named to similiar repositories / package manager
- Publish the release branch on PyPi and NPM (required to check the packaging)
- Analyze linked issues as an anonymous user
- (should publish automatically the release on PyPi and NPM)
- Update the
openimis.jsonin assemblies main branch to use only official version (not rc) - Update demo server
- 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-04
| Expand |
|---|
|
...
|
...
- Check and update Sources Release 2022-04
- Update demo server
- Installation guide / Installation and Country Localisation supports installation of the latest release
- All source components link to the correct repository on GitHub, have the correct version, valid release notes and are reasonably named to similiar repositories / package manager
- Formulate release notes in current release (Releases) and forward it to co-ordination desk for promotion (e.g. newsletter, Twitter)
openimis.json to use only official version (not rc) on assembly modules...