Versions Compared

Key

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

Checklist

GitHub

Releases Page -> Releases

  •  All links are working and are helpful
  •  Dates and status of all releases are correct

Release Page: e.g. Release 2022-04

  •  All links are working and are helpful
  •  Release is marked as “GA” and dates are correct
  •  All relevant tickets are assigned
  •  All assigned tickets are marked “Done”

Release Sources Page: e.g. Sources Release 2022-04

  •  All components are consistently versioned according to Version management
  •  All links are working and helpful
  •  All components link to the correct repository and version
  •  All components have correct “Release Notes”
  •  All components link to reasonably similiar named repositories / package manager

Release notes and Sub Pages

  •  Release notes Shows the latest release notes of all sub pages
  •  All sub pages of Release notes contain the same release notes of the latest version as the repository (at the time of the release)

Sandbox Landscape

Following Release

Findings Release 2022-04

Questions

Content

Table of Contents
minLevel1
maxLevel7
excludeContent

Agenda

Anchor
todos
todos
Work Items

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?)
  •  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
  • 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 ->
  •  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.