Thijs Kinkhorst wrote: > While the package might not be of the quality we strive to achieve within > Debian; if a bug is not release critical we consider the bug not to be > serious enough to impact the packages' releaseworthyness. This is by > definition. Even if there are many of those bugs, they appearently do not > prevent the core functionality from working.
One problem with this definition is that it allows a package's quality to be nickled and dimed to death by hordes of non-RC but variously annoying bugs, to the point that every user of the package will encounter annoying bugs that make the package not worth using, even if which of the many bugs they happen to encounter varies. This is truely annoying in the case where there are multiple packages in Debian to serve a given need, and the user is stuck trying each of them in turn just to find one that is well enough maintained. The only things we have to deal with this right now are a) tasks and b) unwritten lore about which packages to avoid. I think that the RC bug metric is overated and doesn't consider these kinds of effects that end up pulling down the overall usability of Debian. -- see shy jo
signature.asc
Description: Digital signature
