Announcing Mailman 2.0 beta 3
Barry A. Warsaw <bwarsaw <at> beopen.com>
2000-06-29 06:55:12 GMT
Okay folks, I am finally releasing Mailman 2.0 beta 3. I think I have
nailed the duplicates problem -- at least I have seen no duplicates in
the last 24 hours on python.org, so I'm feeling good about it (we'll
see if that lasts tomorrow morning :).
Please give this version a thorough test; I'd like to have a much
shorter release cycle for the next few betas. I am aiming to release
2.0 final on July 14th, the Friday before the O'Reilly OSSCON. I plan
on spending time between now and then on slogging through the
discussion lists and bug reports, and working on the documentation.
See below for an excerpt from the NEWS file for changes since
2.0beta2. If you have not been following the CVS updates and are
upgrading from 2.0 beta 2 or earlier PLEASE READ THE UPGRADING FILE!
A crucial step is to reload your crontab.in file, otherwise you won't
clear your message queue often enough (or perhaps not at all).
-------------------- snip snip --------------------
2.0 beta 3 (26-Jun-2000)
- Delivery mechanism (qrunner) refined to support immediate
queuing, queuing directly from MTA, and queuing on any error
along the delivery pipeline. This means 1) that huge lists
can't time out the MTA's program delivery channel; 2) it is much
harder to completely lose messages; 3) eventually, qrunner will
be elaborated to meter delivery to the MTA so as not to swamp
it. The tradeoff is in more disk I/O since every message coming