On 11.12.2012 07:33, Helmut Grohne wrote:
On Mon, Dec 10, 2012 at 04:12:18PM -0800, Don Armstrong wrote:
Debian policy is the primary document which defines what is a
serious
bug ("it violates a must or required directive".) Additionally, the
RMs and a maintainer can additionally make any bug (or class of bug)
they see making a package unsuitable for release severity serious.
Finally, RMs are the arbiter of what bugs are considered release
critical; they can mark any bug they wish as wheezy-ignore, and it
will be ignored for the purposes of releasing that release.
This represents my reading of the current description as well.
However
it does not represent the current practise. The release team reserves
the right to downgrade issues that they deem not to be release
critical
and only use wheezy-ignore for the very hard cases.
fwiw, I think the central issue here is that neither Policy nor the BTS
documentation actually say that violating a "must or required directive"
merits a serious bug; they each say that a "severe violation" of Policy
merits such a severity and that the two sets of issues are approximately
equal. This may seem slightly picky, but some searching suggests that
the wording used to be more restrictive some years ago.
My understanding is that the decision as to what exactly constitutes a
"severe violation" was at some point in the past delegated by owner@bugs
to the Release Managers; I'm not personally aware of where that might
have been documented, but there's been an RC policy document laying out
what the Release Managers (and later Release Team) believe should be
included published since at least the Sarge release
(<URL:http://release.debian.org/sarge/rc_policy.txt>).
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
