From: Luca Boccassi Date: Thu, 1 Aug 2024 19:35:57 +0000 (+0100) Subject: os-release: change RELEASE_TYPE value from 'pre-release' to 'development' X-Git-Tag: v257-rc1~775^2~1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=67f90b0d85bc425ec2c11106e8270c981c36585a;p=thirdparty%2Fsystemd.git os-release: change RELEASE_TYPE value from 'pre-release' to 'development' The point was made on https://lists.debian.org/debian-ctte/2024/08/msg00005.html that 'pre-release sounds' like an RC candidate, ie, something that will change very slightly in the released version. But this is not necessarily the case for example at the beginnig of a Fedora Rawhide or Debian Testing release cycle, so change it to a more generic 'development' Follow-up for 7102dc52e6b03248da1f01b3a8a4b83c6d7a1316 --- diff --git a/man/os-release.xml b/man/os-release.xml index 28384d352ad..01c2018003e 100644 --- a/man/os-release.xml +++ b/man/os-release.xml @@ -338,14 +338,14 @@ 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 + development 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. experiment is for experimental builds of the system, created specifically to test some work-in-progress feature. This is meant to be used in combination with EXPERIMENT=. If unset, or an unknown value, assume that the release is stable. - Examples: RELEASE_TYPE=pre-release, RELEASE_TYPE=lts. + Examples: RELEASE_TYPE=development, RELEASE_TYPE=lts.