Further bug system stuff...
Well, I've waded through bugs 1000-1303 in the last couple of hours.
I've zapped a few bugs that had apparently been solved but never
checked off, and documented a few duplicates.
I'd like to ask that all maintainers _please_ take some time to check
out your bug lists---I suspect that as daunting a task as that might
seem (and trust me, I know---look at the list for ncurses), you can
probably get rid of half of any list right off the bat because they're
reports of problems on upstream versions that have been fixed already
or some such.
I'd also like some clarification from Bruce and/or Ian J. as to what
they would rather see done in the case of bugs that have probably been
fixed, but can't be verified without a particular hardare setup (the
old BusLogic v. Adaptec issue is the one that comes to mind first).
As I see it, there are two options:
1) Send a message to the originator of the bug report asking him/her
to check and see if the bug still exists, and close the bug report if
its been done, or
2) Mark the bug done, and in the message to the originator, ask them
to reopen it if it still exists.
#1 is obviously the more cautious approach, but, frankly, I don't know
if that is preferable or not.
Mike.
--
"Don't let me make you unhappy by failing to be contrary enough...."
Reply to: