On 01/28/2010 08:29 AM, Alex Hudson wrote:
I don't usually throw in my 2p on subjective issues like this,
but...
On 28/01/10 13:17, Steve Dickson wrote:
> Most of us really take pride in making sure what we push out to
> the community has been tested and will not be disruptive
> or destructive. Then there a small group of people that simply
> don't give a damn what they push out or the havoc they cause.
> This makes the *entire* community look like crap...
>
I think it's a bit unfair to assume less than good faith on the part of
other developers.
Maybe... but it sure seems like this is a systemic problem..
I'm running 3.0.1 right now, I run it pretty hard on some large accounts
and with a variety of mail servers (dovecot for one). I haven't seen
anything like this bug, on any machines I run.
I think it's super-helpful for you to point out potentially really
horrible bugs like this, and I applaud that. But, even though I'm
guessing every tbird 3.0.01 user you've spoken to you has told you it's
eaten their mail, it doesn't seem to have happened here and I would bet
there are other users for whom it's working great. I don't think this is
a case of just "pushing out crap".
I guess I have a different definition
of crap... ;-)
I have been on both sides of these bugs... So I know (the hard way)
when you push something out that breaks existing configurations, its crap!
steved.