DDD Quality Assurance Process

[Andreas Zeller]

Hi!

Zdenek Sekera <zs@sgi.com> writes:

> I've sent this to ddd-bugs over a week ago, I conclude it got
> lost somewhere because normally the answer is back within a few days.
> Or the answer got lost?

Normally, if you're a subscriber of bug-ddd, you get your own message
within a few seconds.  Besides this, there is no confirmation message.

Your bug report is marked `reproduce it as soon as I have nothing else
to do' in my list of DDD bugs.  What does this mean?

1. If a problem gets reported by a DDD user, and I have no chance to
   reproduce it, I raise my eyes to the ceiling in the hope that some
   other helpful soul (i.e. a member of `bug-ddd') will be able to help
   the poor guy out.

2. If I have a chance to reproduce it, I shrug my shoulders and I'll try
   to reproduce it "as soon as I have nothing else to do" (i.e. not
   today, not tomorrow).

3. As soon as the problem is reported by another DDD user, a flash of
   interest runs across my face and I'll try to reproduce it "as soon as
   I can".

4. If it gets reported by a third DDD user, I get a worried look on my
   face: I'll try to reproduce it "now", and I'll try to fix it even if I
   cannot reproduce it.

5. If the bug report encloses a patch, I let out a cry of joy; typically
   I'll check and apply it "right away".  This means that these bug reports
   have highest priority.

So far for the DDD quality assurance process: your report is currently
in category 2, with chances of raising further as soon as someone has
the same problem or suggests a patch.  Not exactly ISO 9001, but being
persistent and constructive helps :-)

Best wishes, and a nice weekend,

Andreas

-- 
Andreas Zeller     Universitaet Passau
                   http://www.fmi.uni-passau.de/st/staff/zeller/