On Sat, 09 Apr 2005, Pierre THIERRY wrote: > Scribit Don Armstrong dies 04/04/2005 hora 01:09: > > Otherwise, all you're doing is abusing the BTS, no matter how correct > > your actual appraisal of the severity bug is. > > Downgrading a bug that is a clear violation of the policy just to > have a package in the next stable release IS abusing the BTS. I'll try to make this really clear: The maintainer is primarily responsible for the severity levels of the bugs in their package. Basically, the only exception[1] to this are the RMs, who may decide that a bug needs to be above or below the RC threshold.[2] Considering the fact that the RMs have weighed in on this matter and have also decided that it is inappropriate for this bug to be RC, as well as the maintainer, you're fresh out of ways to legitimately change the severity of the bug. Just to restate what I said again: If you're changing the severity levels of a bug in a battle with the maintainer, even if your assesment of the severity is correct, all you're doing is abusing the BTS. Don Armstrong 1: Obviously, new information can change the severity of a bug, but if the maintainer changes it, it should stay that way. 2: But even they don't get to override the maintainer's decision if a bug is S, G, or C, or W, M, N, or I. -- Do not handicap your children by making their lives easy. -- Robert Heinlein _Time Enough For Love_ p251 http://www.donarmstrong.com http://rzlab.ucr.edu
Attachment:
signature.asc
Description: Digital signature