Hi, On Fri, 10 May 2013, Paul Wise wrote: > > Comments ? > > I wonder if doing this recursively is a good idea or not. If we decide > to do that, your approach to limit the recursion is a good one.
I also tend to think that doing it recursively is not a good idea in general. Or maybe only for packages which are not widely used and are at risk of getting removed. > I guess you focused on bugs tagged 'help' so that less maintainers are > affected? Is the result very different if you change that to all RC > bugs? Perhaps we could use recursion for bugs tagged 'help' and no > recursion for RC bugs older than one month. A blacklist may be needed > to avoid things like eglibc appearing on all packages containing ELF > binaries though. Increasing the visibility of bugs tagged help is a good idea and thus using recursion in this specific case is probably ok. I would also suggest not displaying bugs where someone is actively taking care of it (i.e. when a owner is set even though it's not often used). I would also suggest to completely ignore RC bugs in package with lots of reverse dependencies, that is until they are tagged help or are getting really old. > It is my feeling that bugs tagged 'help', especially in core packages, > are probably ones that are harder to fix and may not be good targets > for getting people who aren't intimately familiar with the packages to > fix them. I don't think that it's worth trying to filter those at this point. > I think perhaps that limiting the amount of RC bugs filed against deps > to 5 or 10 per PTS page would be good. While I understand the logic "too much and it's going to be useless/ignored", I don't agree that we must put a hard limit. We might have to tweak our rules to avoid too many such cases but then once we have something it should be understandable and relatively complete. Or we must be able to provide a link to get the full list of RC bugs affecting (recursive) dependencies. BTW, I would love if the PTS would make it easier to contact all maintainers of reverse dependencies. Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130510080357.gb16...@x230-buxy.home.ouaza.com