How to do CRITICAL bugs (was: NIS and libc in bo?)
> This problem is Bug#7534. Brian please put this on your list of "critical
> bugs".
Done.
> Anyways, what's the procedure with "critical bugs"? Do you, Brian, check
> all incoming bugs and decide which of them are critical, or should the
> maintainers report to you when they think a bug is critical?
I just maintain the list and add/remove from it as requested by others.
There is no way I could track all of the bugs to know how critical they
are.
People who think a bug in critical should send me the number (preferrably
in the format from the bug tracking page) and a reason why it should be
marked (or unmarked) critical. For example:
---
#7534: netbase 2.09-1 has a broken ypbind
Package: libc5; Reported by: Richard Kaszeta <kaszeta@me.umn.edu>; 16 days old.
Please mark this bug as critical. Unless it is fixed, NIS will not work
at all with release 1.3 of Debian.
---
Brian
( bcwhite@verisim.com )
-------------------------------------------------------------------------------
if you have a 50% chance of guessing right,you will guess wrong 75% of the time
Reply to: