"JRA" == Jay R Ashworth <jra@baylink.com> writes:
JRA> Barry? How far along the garden path *is* 2.1?
It's in alpha, and AFAIK isn't being used by anyone except for testing purposes. In fact there have been zero downloads from SF so I wonder if you all are just ignoring it, or if everyone uses CVS. :)
Still, I'm relatively confident that what's there mostly works (more confident about the new queuing stuff, less so about the i18n stuff).
JRA> I've just gotten shot in the head with a 1000:1 slowdown on
JRA> batch adds for send a welcome vs don't... along with one or
JRA> two other items.
JRA> Time to bring them up? Or past...?
You can always bring them up, but the best place to record them for posterity is in the SF tracker. Put it in the feature requests tracker or bug tracker as appropriate. There's just too much chance that it'll get lost in my inbox.
Or use the wiki for discussion purposes if you want. The wiki already contains what I think I can get to for 2.1. I want to try to be conservative with changes because the i18n stuff really needs to get out there. Still, I think some of the changes I've made already will help get a bunch of new features into the code base.
I use the same approach for Python development -- new features are on the table until the first beta release. I'm trying to keep any changes to the underlying "database" off the table for 2.1 because I think that'll push 2.1 back too far. My best guess at the moment is that we might see a beta of 2.1 by May.
I'll be concentrating on several other projects over the next few weeks though, so Mailman hacking will be a spare-time affair. There's Python 2.1 to work on, and I'm committed to working on BSDDB support for ZODB. This latter may have good side benefits for Mailman 3.0.
There's also some talk about more focussed Mailman work for some clients, but I don't have much information about that at the moment.
-Barry