{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Alex Fuller <[EMAIL PROTECTED]>
I agree wholeheartedly about the thanks, but I think part of the reason
there is such a rush of problems just before a new release is that people
don't want to create too much noise by raising every bug which might occur
in the current TOT build since they're probably actively being worked on, or
come and go on a day to day basis. It's only when things are getting
finalised that you get an idea of what might still be a problem.
It's no good just reporting bugs from the last release version because so
much changes in between - e.g. in this case a new MSN library. Besides we're
nearly all living life dangerously clinging to the top of the tree ;-)
So if this is a problem for the lead developers, what is the solution?
Alex
On 6/3/02 11:41 pm, Steven W. Riggins <[EMAIL PROTECTED]> wrote:
> {#} Replies are directed back to [EMAIL PROTECTED]
> {#} To reply to the author, write to "Steven W. Riggins"
> <[EMAIL PROTECTED]>
>
> Funny how a "we're shipping soon" email can cause so much stir. I wanted to
> thank Colter et al for being patient with us.
>
> Its clear a lot of people have been bugged by stuff but never brought it up.
> One of the beauties of open source and the developers offering this list is
> that it lets us hash things out as a community, something I don't take for
> granted.
>
> So thanks guys, keep up the good work!
>
> Steve
>
> {#} ----------------------------------------------------+[ fire ]+---
>
>
>
>
{#} ----------------------------------------------------+[ fire ]+---
