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.
> Perhaps the confusion is over the fact that bug severity and bug
> RC-ness are not the same thing?
This is indeed a bit confusing. The website mentioned above defines
release critical as anything above important, but does not take ignore
tags into account. Improving on this point without cluttering the
documentation seems hard. Maybe this is why other bug tracking systems
define severities and priorities. Indeed I suggested the usage of ignore
tags to the release team without success.
Helmut
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
