Versions Compared

Key

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

...

Content

Table of Contents
minLevel1
maxLevel7
exclude

...

Content

Agenda

...

Anchor
todos
todos

...

Work Items

...

  •  

...

  • Release 2022-

...

...

Preparation and Deployment

  •  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)
  •  All affected repositories (GitHub, Pypi.org, http://npmjs.com , etc.) are tagged and versioned according to Version management (Versioning to be discussed in detail in a future session)

Releases Page Releases

  •  Analyze linked issues as a normal user (private projects hidden)
  •  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” or pushed to the next release
  •  Epics align with the “Highlights” of the release

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

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)

User Documentation

Installation Guide / Configuration / Other

Sandbox Landscape Sandbox Landscape

Post-Release

  •  Release Page (e.g. Release 2022-04) for the following release is set up and appears correctly on Releases
  •  Relevant Epics for the new release were created in Jira and added to the Release Page

...

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

...

  • explanation, 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

...

...

  •  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”

...

...

...

  • redundancy and confusion
  •  Clarify wording redundancy “openIMIS …” for components, modules, wiki pages, etc.