We have a release process... we voted on a release plan, and the code is now frozen. If we see a bug, we raise it, discuss it, and vote whether we should fix it. You don't like this process and want to use your own, and I can't get around your veto.
You're just not making very many friends by changing rules and -1 everything you don't want to work on. I voted to support the 2.1 release plan and code freeze without new rules being introduced. Anyway, I was very supportive of someone bringing rigor to our testing, documentation, and release process. I'll admit I'm upset this moment, but I'm going to find it difficult to +1 to any more of your release plans with the way the past month has gone. And finally, this is a simple bug and I'm not going to sit here and talk for days about how to go about this change... I said this is a quick fix, maybe a bit more to support backwards compatibility. I think you're being clearly beligerent about the QA issue... pop3 file system DOES NOT WORK!!! To your comment of it being usable as a simple test configuration... who downloads a mail server for a simple test configuration? By comparison I suppose you would say if the SMTP handler couldn't support remote connections, that's acceptable? > > My view was that if Noel was set with his issues that we'd call for a final > release vote and get this thing out the door. Obviously, that would be in... Heh, well if you're expect us to need another vote to make the final release, you can expect a very loud -1 from me. I'm so tired of always arguing within this project. Why can't we all just get along? We've had a number of users immediately say they want this bug fixed when I asked for a vote to do so.... why do we have to argue so much?!? Serge -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
