It's very helpful if the folks who originally reported bugs test the fix,
using their own data and environment, just in case what the developers
found isn't exactly the same problem you're actually seeing in the field.
If you do so and the fix solves the problem, then yes, marking it VERIFIED
is appreciated.
If you don't, the general assumption is that "silence eventually gives
consent".
(I've been known to mark bugs CLOSED as soon as I check in the fix, when
I'm sufficiently sure it's actually the right change. Officially, I think
that's considered sloppy practice. The better approach is for the
developers to append a "fix posted, please verify" note to the Bugzilla
entry and wait a reasonable time for either thanks or objections before
closing the bug..)
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
