summaryrefslogtreecommitdiffstats
path: root/man/os-release.xml
diff options
context:
space:
mode:
Diffstat (limited to 'man/os-release.xml')
-rw-r--r--man/os-release.xml23
1 files changed, 23 insertions, 0 deletions
diff --git a/man/os-release.xml b/man/os-release.xml
index afdb21fc57..32edc088df 100644
--- a/man/os-release.xml
+++ b/man/os-release.xml
@@ -325,6 +325,29 @@
<xi:include href="version-info.xml" xpointer="v249"/></listitem>
</varlistentry>
+
+ <varlistentry>
+ <term><varname>RELEASE_TYPE=</varname></term>
+
+ <listitem><para>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:
+ <literal>stable</literal> 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.
+ <literal>lts</literal> 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.
+ <literal>pre-release</literal> 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 <literal>stable</literal>.</para>
+
+ <para>Examples: <literal>RELEASE_TYPE=pre-release</literal>, <literal>RELEASE_TYPE=lts</literal>.
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v257"/></listitem>
+ </varlistentry>
</variablelist>
<para>To summarize: if the image updates are built and shipped as comprehensive units,