...
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Agenda
Cleanup subdomains / DNS-records
Review and delete finished Work Items
Review Findings in Release Checklist for Maintainer [Draft] - Release 2022-04
Discuss Future Improvements and agree on next Work Items
...
- STPH: Document list of steps aligned to phases on Release 2022-10 into Release Checklist for Maintainer [Draft] - Release 2022-04 and restructure the checklist accordingly
- 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
- STPH: Installation Guide (Video) / One-Click-Install / Step-by-Step-Instructions
- STPH: Review Findings Fix findings in Release Checklist for Maintainer [Draft] - Release 2022-04 and fix if possible
Coming up next
- Agree on Checklist in Release Checklist for Maintainer [Draft] - Release 2022-04
- Fix Findings in Release Checklist for Maintainer [Draft] - Release 2022-04Integrate Release Checklist for Maintainer [Draft] - Release 2022-04 in Release 2022-04 and prepare clean copy of the checklist for Release 2022-10
- Get an overview of Youtube-Content (up2date? helpful? misleading?)
...
- Dedicated page for each module under openIMIS Modules (with Page Properties, descriptions/basic explainationexplanation, 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 components on Release 2022-04 according to Modules ->
- Include repository info instead of redundancy (and info gaps) between https://openimis.atlassian.net/wiki/spaces/OP/pages/368345128 and repositories on GitHub (PlugIn?)
- Clarify usage of Pypi.org and npmjs.org with GitHub (calcrule links to GitHub, others to PyPi)
- Update Installation Guides (Docker and Non-Docker)
- Dependency Graph for modules / consistent dependency information in Sources Release 2022-04
- Reevaluate “Testing openIMIS” on Sources Release 2022-04
- Consider “Legacy” modules as “Deprecated” on Sources Release 2022-04
- Sort components by name on Sources Release 2022-04?
- Release 2022-04 Reevaluate redundant information in “Highlights” and “Release Notes”
- Combine Releases / Release 2022-04 , https://openimis.atlassian.net/wiki/spaces/OP/pages/368345128 and Sources/Sources Release 2022-04 to reduce structural redundancy and confusion
- Clarify wording redundancy “openIMIS …” for components, modules, wiki pages, etc.
...