> > I'm still pretty stressed about the whole CPU thing I went through
> recently
>
> In fairness, you raised the issue on Sunday, posted a stack trace on
> Tuesday, and were fixed on Wednesday.  In retrospect, when I
> saw your post
> on Tuesday, I had some concerns about the bug being in the DNS code; I
> should have followed up on that feeling, but this is one of
> the only real
> bugs we’ve ever encountered in his code.  Ironically, he had fixed it
> earlier, and I’d thought to put in a newer version of his
> code, but when I
> had looked at his web site, he already had a fix for new bug
> in a version we
> didn’t have, so I figured that we could wait for his
> development to settled
> down before we moved forward.
>
>       --- Noel

Where in the commercial world would a new and relatively obscure bug such as
this be diagnosed and fixed in this time-frame? I would rather view this in
a positive light, as a demonstration of how effective OSS can be.

Noel, with the benefit of hindsight you are seeing how the bug might have
been removed earlier, but that doesn't imply a lack of foresight. And let's
remember, we're talking about an alpha release of James here.

-- Steve


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to