Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Content

Table of Contents
minLevel1
maxLevel7
excludeContentsContent

Agenda

Anchor
todos
todos
Work Items

  •  STPH: Document list of steps aligned to phases on Release 2022-10 into Release / Completely mark off all todos on 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
  • 10
    •  Collecting (writing) documentation
      •  Insuree batch
      •  Insuree self registration (from Nepal)
    •  Add epics and include features/fixes on release page
    •  Quick check sandbox
    •  Documentation
  •  Include logo on the wikipedia page (what copyright shall we use?)
  •  Installation Guide (IG):
  •  STPH: Do Post-Release of Release 2022-10
  •  STPH: Installation Guide (Video) / One-Click-Install / Step-by-Step-Instructions
  •  STPH: Review Findings in Release Checklist for Maintainer [Draft] - Release 2022-04 and fix if possible
  •  Agree on Checklist in Release Checklist for Maintainer [Draft] - Release 2022-04
  •  Fix Findings in Release Checklist for Maintainer [Draft] - Release 2022-04
  •  Integrate Release Checklist for Maintainer [Draft] - Release 2022-04 in Release 2022-04 and prepare clean copy of the checklist for Release 2022-10

Questions

  •  How do we keep the version (link) of every component in Sources Release 2022-04 in sync with every component’s “Release notes” page (e.g. openIMIS Database release notes) as well as with what is actually in the repository?
  •  How can we define “Epics” that represent better the added value (see mismatch between Release 2022-04 Epics and Highlights)?

Talking Points Installation Guide

  •  Docker Installation Video is not embedded in the IG
  •  Define Requirements of the IG
    •  Is Simple and complete - Can be followed without knowing the tools
    •  Is fully documented on one platform (Wiki) and free of redundancies
    •  Works (= is tested) in all supported scenarios (e.g. platforms, OS version, databases)
    •  Installation with Docker
    •  Version update guide
    •  Version upgrade guide Legacy → Modular / MS SQL → PostgreSQL (DeepDive)
    •  
    •  Focus on standard installation (Linux (Debian-based) 64-bit, (specific version with LTS), PostgreSQL)
    •  Community Installation Blog with individual installation experiences (Maybe as part of 4. Installation test in Test cases overview)
      •  Non-Docker
      •  Windows etc.
    •  Multi-OS (Windows, Linux, 32/64 Bit, including a reasonable range of versions) capable
    •  Multi-DB (MS SQL, PostgreSQL) capable
    •  Multilanguage capable
    •  Minimum Requirements are documented
    •  Legacy Installation Guide is exluded and/or archived
  •  Future outlook of deployment / installations

Anchor
future
future
Future Improvements

  •  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 Release notes 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 , Release notes and Sources/Sources Release 2022-04 to reduce structural redunancy redundancy and confusion
  •  Clarify wording redundancy “openIMIS …” for components, modules, wiki pages, etc.

...