Re: Bug mass filling

[Mike Hommey <mh@glandium.org>]

On Thu, Oct 19, 2006 at 09:17:38PM +0200, Andreas Barth <aba@not.so.argh.org> wrote:
> * Mike Hommey (mh@glandium.org) [061019 21:14]:
> > On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth <aba@not.so.argh.org> wrote:
> > > * Mike Hommey (mh@glandium.org) [061019 20:42]:
> > > > Note how subtly the Etch RC policy removes the first alternative of the
> > > > serious bug description...
> > > 
> > > Which do you mean? Please read the Etch RC policy. It tells:
> > > | 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
> > > 
> > > So, what does the Etch RC policy remove from the bugs.d.o description?
> > 
> > 'is a severe violation of Debian policy (roughly, it violates a "must" or
> >  "required" directive), or'
> 
> The html-code for this part is:
> <DT><CODE>serious</CODE>
> <DD>is a <a href="http://release.debian.org/etch_rc_policy.txt";>severe
> violation of Debian policy</a> (roughly, it violates a "must" or "required"
> directive), or, in the package maintainer's opinion, makes the package
> unsuitable for release.
> 
> So, obviously http://www.debian.org/Bugs/Developer#severities defines
> that "severe violation of Debian policy" means anything referenced in
> the etch_rc_policy-document.

Yeah, right, whatever, as soon as etch is release on December 4th...