Julien Cristau <jcris...@debian.org> writes: > On Tue, Nov 24, 2015 at 06:14:43 +1100, Ben Finney wrote: > > > If it's a “severe violation of Debian policy”, the bug is at least > > “serious” severity.
This is one way that a bug can be determined “Severity: serious”, by definition. In other words: “severe violation of Debian policy” implies “bug is Severity: serious”. > The release team's RC policy decides which policy violations we > consider "severe" in the sense of "gets a serious severity bug". And this is another, by definition. In other words: “release team determined the bug is RC” implies “bug is Severity: serious”. The reverse implication is not true: one cannot infer from “Severity: serious” that the release team made that determination. The “Severity” field doesn't *only* mean that, so it's not a valid inference. By my reading of the “serious” severity definition, any of its “or” clauses makes for sufficient justification to set “Severity: serious” without considering the other clauses. -- \ “If this is your first visit to the USSR, you are welcome to | `\ it.” —hotel room, Moscow | _o__) | Ben Finney
