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 28384d352adf0f60c354ad36c550d7427282fc85..01c2018003ed2d37b103b042a40f9862a3dabe64 100644 (file)
--- 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.
-          <literal>pre-release</literal> is for unstable versions of the system, unsuitable for production
+          <literal>development</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.
           <literal>experiment</literal> 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 <varname>EXPERIMENT=</varname>.
           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>Examples: <literal>RELEASE_TYPE=development</literal>, <literal>RELEASE_TYPE=lts</literal>.
           </para>
 
           <xi:include href="version-info.xml" xpointer="v257"/></listitem>