On Thu, 2006-10-19 at 19:51 +0200, Mike Hommey wrote: > On Thu, Oct 19, 2006 at 07:36:27PM +0200, Andreas Barth <[EMAIL PROTECTED]> > wrote: > > > Doesn't policy violation warrant Critical severity? > > > > No. Please see the top of http://release.debian.org/etch_rc_policy.txt > > for which bugs are critical, grave and serious. > > That is irrelevant for the severity of bugs. [...] > Don't change severities for releasing-in-time purposes. There is
Erm... the release team have been the arbiters of what merits an RC severity since at least before Sarge was released. >From http://www.debian.org/Bugs/Developer#severities: "Certain severities are considered release-critical, meaning the bug will have an impact on releasing the package with the stable release of Debian. Currently, these are critical, grave and serious. For complete and canonical rules on what issues merit these severities, see the list of Release-Critical Issues for Etch." The top of the latter page reads "The purpose of this document is to be a correct, complete and canonical list of issues that merit a "serious" bug under the clause "a severe violation of Debian policy". In addition to the issues listed in this document, an issue is release critical if it: [...] * in the maintainer's opinion, makes the package unsuitable for release (these issues are "serious" severity) " i.e. if it's not in the policy and doesn't meet the above definition, it's *not* severity serious or higher. I'd suggest reading http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=277074;msg=72, in which a current member of [EMAIL PROTECTED] (and at the time an RM) confirms that a member of the ftp-master team was correct in stating the above. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]