improved process for users to update wis2box to latest release

[maaikelimper]

Based on the feedback from users during the recent WIS2 Training workshop, we should review how to improve the process of updating wis2box to the latest release

[maaikelimper]

adding the label "security" as we need a process to allow users to easily update wis2box when vulnerabilities are found.

[tomkralidis]

2024-11-21: brainstorming:

• define a process to pull updates between releases
• add a "check for updates" capability to identify new releases

Delineate update concepts:

• software updates

• content updates (configurations, tables)

• major/minor/patch

• patch releases are for:

  • bugfixes
  • configuration updates
  • tables/schemas updates

WMO FT cycle:

• 2x/year

• WIS2

• WIGOS

• BUFR/GRIB

• wis2box updates would listen on bugfix releases only (based on WMO FT)

• wis2box image stable branches

What is a patch

• artifacts
  • anything resulting from WMO FT
  • wis2box configurations
• software
  • bug fixes

Decisions

• all wis2box repositories are managed with branches:
  • main branch (master/tip)
  • stable branches (patch releases)
• in each repository, changes to stable branches can feed into a patch release via backporting
• wis2box-ctl.py script updated to include the following:
  • for a given MINOR release, compare/detect available update
  • present the user with the list of images that can be updated
  • user accepts, docker pull, wis2box-ctl restart
• any updates of this type are bound to the same MINOR release version only