Bug#1144046: define term 'release critical'?

Simon Josefsson <[email protected]> Wed, 12 Aug 2026 13:17:50 +0200

Newsgroups	gmane.linux.debian.devel.policy
Message-ID	<87jypvio4h.fsf__43118.5686773219$1786533570$gmane$org@josefsson.org>

Andrey Rakhmatullin <[email protected]> writes:

> On Mon, Aug 10, 2026 at 09:41:55AM +0200, Simon Josefsson wrote:
>>I couldn't find a good reference of what a 'release critical' bug means,
>
> The wording suggests that it's a term external to the Policy.
>
>>would it be reasonable to include this in the policy manual?
>
> If this part causes confusion it could be moved to a footnote I guess?

I've always been uncertain if the definition of a 'release critical bug'
should be considered:

1) Any bug with severity critical, grave, or serious.

2) A bug that fulfills the ever-moving definition in
https://release.debian.org/testing/rc_policy.txt

3) Something else.

Is there a simple clear definition?

Defining it as 1) above would solve my concern and is simple, but I'm
honestly not certain this is actually how everyone interprete the term.

A footnote is fine for me.

Or some acknowledging that there is no consensus that this is worthy of
adding an definition to Debian Policy for, and that the term is
something that is only relevant in a narrow part of Debian (i.e., for
the release process).  Still, I find the term 'release critical bug' or
RC-bug is often used generally about any package, which should warrant a
better definition.

>>Or is that a more relaxed term that is continously re-defined in
>>https://release.debian.org/testing/rc_policy.txt ?
>
> This document defines what is considered release critical, not what
> being release critical means.

That is my interpretation too -- but then a definition is lacking.  A
random text file on a random *.debian.org host also isn't the best place
to document things on.

/Simon

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