* Sandro Tosi <mo...@debian.org>, 2011-04-10, 15:54:
- reassign all those bugs to the most recent source pro: immediate action
IMO this should be done only if number of bugs is low (say, less than 5 per maintainer).
what version information to use?
In many cases we have this information is in the BTS (e.g. the bug is assigned to an nonexistent package, but is marked as found in a source package that is still there).
- notify the maintainer to triage those bugs pro more knowledgeable look at them con if they didn't care to do at RM time, what should they do now? likely to not receive any answers (at all or in a timely fashion)
I wouldn't assume the worst. Hopefully the maintainers will take care of their bugs after a gentle reminder.
how notification should be done: private email (no public trace), a bug (another one), else?
For a starter, I'd send a message to debian-devel@ with dd-list and see what happens. :)
-- Jakub Wilk -- 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/20110412005834.ga5...@jwilk.net
