icinga2/.github/ISSUE_TEMPLATE/release.md
Julian Brost 5b3cb10a8f Release issue template: docker-icinga2 is only required for pre-2.16
Starting with v2.16, container images are built from within this repo without
using the docker-icinga2 repo. Thus, updates there are only relevant if an
older version is released.
2026-04-22 14:41:15 +02:00

1.8 KiB

name about title labels assignees
[INTERNAL] Release Release a version Release Version v$version

Release Workflow

  • Update ICINGA2_VERSION
  • Update bundled Windows dependencies
  • Harden global TLS defaults (consult https://ssl-config.mozilla.org)
  • Update CHANGELOG.md
  • Update doc/16-upgrading-icinga-2.md if applicable
  • Create and push a signed tag for the version
  • Build and release DEB and RPM packages
  • Build and release Windows packages
  • Only for releases of versions older than v2.16: Merge dependency updates in https://github.com/Icinga/docker-icinga2/pulls
  • Create release on GitHub
  • Update public docs
  • Announce release
  • Forward-port the CHANGELOG changes to master

Update Bundled Windows Dependencies

Update packages.icinga.com

Add the latest Boost and OpenSSL versions to https://packages.icinga.com/windows/dependencies/, e.g.:

Update Build Server, CI/CD and Documentation

Re-provision Build Server

Even if there aren't any new releases of dependencies with versions hardcoded in the repos and files listed above (Boost, OpenSSL). There may be new build versions of other dependencies (VS, MSVC). Our GitHub actions (tests) use the latest ones automatically, but the GitLab runner (release packages) doesn't.