TestImagePolicy

Cockpit runs tests against many distribution test images. This document collects our lifecycle policy of them.

Fedora

• fedora-coreos: based on the 'testing' stream and automatically rebases on a newer Fedora release
• fedora-rawhide: image used for debugging Testing Farm rawhide builds, rolling release.
• fedora-$RELEASE: (e.g. fedora-44): We support andd release to the latest two branched/stable releases at the same time. We switch to a new Fedora when the Beta/RC release is out and drop the oldest Fedora image. This happens both in the test maps as well as in packit.yaml release policies.

RHEL

• rhel-X-Y: We support all current RHEL major releases. The latest Y stream is built from the nightly development composes, i.e. that is the one that will be released in the future (in the next 6 months). Additionally, since RHEL also has long-term support for even Y streams, we have older images for these as well. Currently only subscription-manager-cockpit actually uses these, though.

CentOS

• centos-X: We support all current CentOS major releases, they are rolling.
• centos-X-bootc: Corresponding bootc variants.

Debian

• debian-testing: rolling release image tracking Debian's testing repository.
• debian-$CODENAME: (for example debian-trixie) - tracks Debian's latest release, see Debian release lifecycle

Ubuntu

• ubuntu-YYMM: We support the current and previous LTS (which is nice for beiboot support). Once the next LTS arrives, we drop support for the oldest one. See the Ubuntu release lifecycle
• ubuntu-stable: The latest release (with short 9 month support). Not really for users, but good to spot problems early on before they hit LTS. We often update that to the development release after the feature freeze, to spot problems even earlier.

Arch Linux

• arch: rolling release image, for help feel free to ask @jelly on Matrix.

OpenSUSE

• Tumbleweed: rolling release image, maintained by the OpenSUSE team.