From: Adrian Vovk Date: Wed, 22 May 2024 22:06:54 +0000 (-0400) Subject: os-release: Add RELEASE_TYPE= X-Git-Tag: v257-rc1~777^2~1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7102dc52e6b03248da1f01b3a8a4b83c6d7a1316;p=thirdparty%2Fsystemd.git os-release: Add RELEASE_TYPE= This will allow GUIs to customize their behavior a little based on the type of release. For example, an OS installer may display a warning/disclaimer if RELEASE_TYPE=prerelease. The software updates app might be a bit more insistent about upgrading to the next major release if RELEASE_TYPE=stable than if RELEASE_TYPE=lts --- diff --git a/man/os-release.xml b/man/os-release.xml index afdb21fc57b..32edc088df3 100644 --- a/man/os-release.xml +++ b/man/os-release.xml @@ -325,6 +325,29 @@ + + + RELEASE_TYPE= + + A lower-case string (no spaces or other characters outside of 0-9, a-z, ".", + "_", and "-"), describing what kind of release this version of the OS is. Known values follow: + stable is for normal releases of the system, suitable for production use. + Generally, stable releases become end-of-life soon after the next major stable release is out. + Examples include Fedora 40, Ubuntu 23.10, OpenSUSE Tumbleweed, and Arch Linux. + lts is for long term support releases of the system, suitable for production + use and supported for an extended period of time. Generally, LTS releases continue to recieve + support even if newer major releases of the distribution are available. Examples include Ubuntu + 24.04, Debian 12 Bookworm and RHEL 9.4. + pre-release is for unstable versions of the system, unsuitable for production + use, such as alpha, beta, or rolling unstable releases. Examples include Fedora Rawhide, Debian + Testing, Fedora 40 Beta, and GNOME OS Nightly. + If unset, or an unknown value, assume that the release is stable. + + Examples: RELEASE_TYPE=pre-release, RELEASE_TYPE=lts. + + + + To summarize: if the image updates are built and shipped as comprehensive units,