Bug#1144046: define term 'release critical'?

Simon Josefsson <[email protected]> Mon, 10 Aug 2026 09:41:55 +0200

Newsgroups	gmane.linux.debian.devel.policy
Message-ID	<87y0eeo20s.fsf__26297.1468315058$1786347804$gmane$org@josefsson.org>

Package: debian-policy
Version: 4.7.4.1
Severity: wishlist

Hi

I couldn't find a good reference of what a 'release critical' bug means,
would it be reasonable to include this in the policy manual?

Or is that a more relaxed term that is continously re-defined in
https://release.debian.org/testing/rc_policy.txt ?

/Simon

0001-Mention-term-release-critical.patch (text/x-diff, 1005 B)

From da250ca3b3102594f2d3fad16116acd1b7bd8f60 Mon Sep 17 00:00:00 2001
From: Simon Josefsson <[email protected]>
Date: Mon, 10 Aug 2026 09:36:52 +0200
Subject: [PATCH] Mention term 'release critical'

---
 policy/ch-scope.rst | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/policy/ch-scope.rst b/policy/ch-scope.rst
index a279c26..58f1df1 100644
--- a/policy/ch-scope.rst
+++ b/policy/ch-scope.rst
@@ -39,7 +39,8 @@ describe the importance of each statement:  [#]_
   to these requirements will generally not be considered acceptable for
   the Debian distribution. These statements correspond to the *critical*,
   *grave*, and *serious* bug severities (normally serious). They are
-  collectively called *Policy requirements*.
+  collectively called *Policy requirements* and sometimes refered to as
+  *release critical*.
 
 * The terms *should* and *should not*, and the adjective *recommended*,
   denote best practices. Non-conformance with these guidelines will
-- 
2.54.0

signature.asc (application/pgp-signature, 1.2 KB)