I'm very much sick of 2.1. I don't know why it's taking so long, but I'm not helping enough to complain.
BUT ANYWAY...
You dodged the issue of whether this was an important bug by saying it was "discussed over and over and over again". Rather than doing so indirectly, I'd prefer if it you directly answered whether you would prefer to ship 2.1 with an unusable configuration (POP3 on, and using file mailstore) or fix this bug.
I understand your frustration with a possible delay. But the feature is glaringly broken, and in my mind it is worth fixing. I think holding people accountable for knowing 100% of what needs to be done in an onsite project is unrealistic at best, and doing so for a globally diverse group of volunteers is even more dangerous.
--
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com
Peter M. Goldstein wrote:
All, IMHO, this is ridiculous.If the bug is glaring now, it was glaring when we discussed the list of bugs for release. And when it's come up on the list before. Again and again and again. There was a conscious decision (with discussion) to defer this bug because we're intending to redo the repositories. Consider this a -1 vote on further delaying the release for something we've discussed over and over and over again. If you want to update the 2.1 POP3 docs to clarify this issue, that would be fine. If you want to put out a 2.2 with this fix, great. Please do it after the seemingly endless 2.1 is out the door. But personally I'm just plain sick of 2.1 and want to be done with it. --Peter
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
