Necessary steps for “Preparation and Deployment” are documented and up-to-date (deliverables, pull-requests, version control & tagging, package manager, testing, staging, configuration, update release documentation, update architecture documentation, update sandbox landscape, etc)
STPH: Lead discussion of version management → Developer Committee
STPH: Archive Wiki-Release notes and update columns in Sources Table
Every component needs to have a link to the related latest release on GitHub in the field “Version / Release Notes”
Every component should have a link to the related package manager in the field “Package Manager”
If every component of a sub table has a valid entry in “Version / Release Notes” that points towards release notes in GitHub, the column “Release Notes” can be deleted
How can we define “Epics” that represent better the added value (see mismatch between Release 2022-04 Epics and Highlights)?
Future Improvements
Dedicated page for each module under openIMIS Modules (with Page Properties, descriptions/basic explaination, version history - Based on release notes pages?)
Clarify wording module / component / repository - Define and document for example “Claim AI” from different perspectives - “Claim AI” Module contains the Components “Claim AI BE” and “Claim AI FE” “?
openIMIS Feature: One-Click-Installation with selection of modules instead of installing components one by one / Define Standard-Installation
Rethink grouping of Components on Release 2022-04 according to Modules ->