RELEASED GNU Mailman 3.0 alpha 3 (Working Man)
I am happy to announce the release of the third alpha version of
Mailman 3, code named "Working Man".
This is primarily a preview release so that developers and other
interested people can download the code and participate in Mailman 3's
further development. I believe we are on track for a final release by
the end of the year, and your contributions of code, feedback,
documentation, etc. will be welcome and appreciated!
Please note that this is an alpha release and as such is not ready for
production use.
You can get the code from the Cheeseshop:
http://pypi.python.org/pypi/mailman/3.0.0a3
Mailman 3 is buildout based and requires Python 2.6. To build it, run
this after unpacking the tarball and cd'ing into it
% python bootstrap.py % bin/buildout
From there you can run the tests
% bin/test
and build the documentation
% bin/docs
Highlights in this release include the start of a REST admin server
for integrating Mailman with external web sites, a combined bin/
mailman uber-command, configuration now done through ini-files using
lazr.config, and better LMTP support.
Enjoy, -Barry
Barry Warsaw wrote:
I am happy to announce the release of the third alpha version of
Mailman 3, code named "Working Man".
Way to go Barry!!
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
- Barry Warsaw <barry@list.org>:
I am happy to announce the release of the third alpha version of Mailman 3, code named "Working Man".
"I guess that's what I am ..." <http://www.youtube.com/watch?v=h59mDlBSt7o>
Congratulations!
p@rick
On Aug 22, 2009, at 1:40 AM, Patrick Ben Koetter wrote:
- Barry Warsaw <barry@list.org>:
I am happy to announce the release of the third alpha version of Mailman 3, code named "Working Man".
"I guess that's what I am ..."
Thanks Patrick, and everyone!
Patrick, I was going to award you the prize for first guessing of the
naming scheme. But then I remembered you had insider information :).
-Barry
- Barry Warsaw <barry@list.org>:
I am happy to announce the release of the third alpha version of Mailman 3, code named "Working Man".
Congratulations!
Highlights in this release include the start of a REST admin server for integrating Mailman with external web sites, a combined bin/mailman uber-command, configuration now done through ini-files using
lazr.config, and better LMTP support.
I'm really looking forward not only to the REStful implementation of the admin server but to the design specs for the web UI I've seen so far, too.
Keep up the good work Stefan
On Aug 22, 2009, at 4:23 AM, Stefan Förster wrote:
I'm really looking forward not only to the REStful implementation of the admin server but to the design specs for the web UI I've seen so far, too.
Yep! Patrick and his team have a nice start to this, and should be
bringing it to the mailing list soon.
-Barry
Shouldn't these release messages for 3.0 alphas redirect to mailman-developers?
Barry Warsaw writes:
Please note that this is an alpha release and as such is not ready for
production use.You can get the code from the Cheeseshop:
And do what with it? Check it in to a git repo, right? I mean, you did say you were looking forward to content contributions! ;-)
So, let's be modern and check it out from Launchpad.
Problems:
(1) Debian stable doesn't have Python2.6. *sigh* (Not your fault, but it's now 0237, and I'm in a bitchin' mood and even Pure Prairie League doesn't make me feel better.)
(2) README.txt refers to a bunch of files in docs/readme/ that don't exist (including the directory itself). If you're planning to reorganize the docs directory, now might be as good a time as any to fix the README. If you plan to populate it instead, you could add a note that volunteers to write the as yet nonexistent docs would be welcome.
(3) docs/ALPHA.txt says you need an unofficial branch of lazr.config ... which doesn't seem to exist:
$ bzr branch lp:~barry/lazr.config/megamerge
You have not informed bzr of your Launchpad ID, and you must do this to
write to Launchpad or access private data. See "bzr help launchpad-login".
http://bazaar.launchpad.net/~barry/lazr.config/megamerge/ is permanently redirected to
https+urllib://bazaar.launchpad.net/~barry/lazr.config/megamerge/
bzr: ERROR: Not a branch: "http://bazaar.launchpad.net/~barry/lazr.config/megamerge/".
Oh, OK, it's private data or something. OK, so we try telling bzr
about our LP ID and try again:
$ bzr branch lp:~barry/lazr.config/megamerge
The authenticity of host 'bazaar.launchpad.net (91.189.90.11)' can't be established.
RSA key fingerprint is 9d:38:3a:63:b1:d5:6f:c4:44:67:53:49:2e:ee:fc:89.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'bazaar.launchpad.net,91.189.90.11' (RSA)
to the list of known hosts.
Permission denied (publickey).
bzr: ERROR: Connection closed: Unexpected end of message. Please check
connectivity and permissions, and report a bug if problems persist. *sigh* I guess I'll just be a good little boy and get the PyPI package, but ... nah, I'll just go to bed and when I wake up I'll discover it was all a bad dream, right?
On Sun, Aug 23, 2009 at 03:25 +0900, Stephen J. Turnbull wrote:
Shouldn't these release messages for 3.0 alphas redirect to mailman-developers?
Barry Warsaw writes:
Please note that this is an alpha release and as such is not ready for
production use.You can get the code from the Cheeseshop:
And do what with it? Check it in to a git repo, right? I mean, you did say you were looking forward to content contributions! ;-)
So, let's be modern and check it out from Launchpad.
Problems:
(1) Debian stable doesn't have Python2.6. *sigh* (Not your fault, but it's now 0237, and I'm in a bitchin' mood and even Pure Prairie League doesn't make me feel better.)
Neither does Debian testing aka squeeze, as I noticed moments ago. Just another reason to run Ubuntu 9.04 or above.
Regs Siggy
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org+ |55 days until|Open Source in Northern Germany: www.free-it.org| |www.Ubucon.de| tech contact: bsb@free-it.de| +-------> ceterum censeo javascriptum esse restrictam <--------+
Bernd Siggy Brentrup writes:
Problems:
(1) Debian stable doesn't have Python2.6. *sigh* (Not your fault, but it's now 0237, and I'm in a bitchin' mood and even Pure Prairie League doesn't make me feel better.)
Neither does Debian testing aka squeeze, as I noticed moments ago. Just another reason to run Ubuntu 9.04 or above.
It's taken me years to get Debian under control so that it installs what I need and only that. No, I don't think I'm going to switch to a distro whose goal is to eliminate the need for Windows.
Hi Stephen,
On Sun, Aug 23, 2009 at 09:48 +0900, you wrote:
Bernd Siggy Brentrup writes:
Problems:
(1) Debian stable doesn't have Python2.6. *sigh* (Not your fault, but it's now 0237, and I'm in a bitchin' mood and even Pure Prairie League doesn't make me feel better.)
Neither does Debian testing aka squeeze, as I noticed moments ago. Just another reason to run Ubuntu 9.04 or above.
It's taken me years to get Debian under control so that it installs what I need and only that. No, I don't think I'm going to switch to a distro whose goal is to eliminate the need for Windows.
Sorry if I sounded like urging you to switch to Ubuntu, my statement was meant only as a pun towards certain people currently in charge at the Debian project I had my issues with.
Looking at the python2.6[1] page in Debian's PTS you'll notice it is still in experimental so don't hold your breath waiting for it appearing in testing.
Regards Siggy
[1] http://packages.qa.debian.org/p/python2.6.html
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org+ |54 days until|Open Source in Northern Germany: www.free-it.org| |www.Ubucon.de| tech contact: bsb@free-it.de| +-------> ceterum censeo javascriptum esse restrictam <--------+
Hi Bernd,
Bernd Siggy Brentrup writes:
Looking at the python2.6[1] page in Debian's PTS you'll notice it is still in experimental so don't hold your breath waiting for it appearing in testing.
I didn't plan to. I don't actually mind installing my own Python. It's just that I've been procrastinating about doing something active on MM3 for months, and on the spur of the moment decided NOW was the time. I wasn't expecting that I'd be spending an hour or so just installing Python (I needed to install a bunch of -dev packages, etc.) and was frustrated. :-þ
On Aug 23, 2009, at 4:34 AM, Stephen J. Turnbull wrote:
Looking at the python2.6[1] page in Debian's PTS you'll notice it is still in experimental so don't hold your breath waiting for it appearing in testing.
I didn't plan to. I don't actually mind installing my own Python. It's just that I've been procrastinating about doing something active on MM3 for months, and on the spur of the moment decided NOW was the time. I wasn't expecting that I'd be spending an hour or so just installing Python (I needed to install a bunch of -dev packages, etc.) and was frustrated. :-þ
Steve, it will be awesome to get your input on MM3. I /think/ you
should be able to do a straight up from-source Python 2.6 install, and
then run the instructions on the ALPHA.txt page. If you hit any
glitches, please do let me know.
-Barry
On Aug 23, 2009, at 12:34 AM, Bernd Siggy Brentrup wrote:
Looking at the python2.6[1] page in Debian's PTS you'll notice it is still in experimental so don't hold your breath waiting for it appearing in testing.
Dang. Too bad Python is so hard to install from source. <wink>
-Barry
On Aug 22, 2009, at 2:25 PM, Stephen J. Turnbull wrote:
Shouldn't these release messages for 3.0 alphas redirect to mailman-developers?
They should, yes. The next ones will.
Barry Warsaw writes:
Please note that this is an alpha release and as such is not ready
for production use.You can get the code from the Cheeseshop:
And do what with it? Check it in to a git repo, right? I mean, you did say you were looking forward to content contributions! ;-)
:)
(2) README.txt refers to a bunch of files in docs/readme/ that don't exist (including the directory itself). If you're planning to reorganize the docs directory, now might be as good a time as any to fix the README. If you plan to populate it instead, you could add a note that volunteers to write the as yet nonexistent docs would be welcome.
I've done some reorganization of the documentation. The doc build
process is a little wonky still, as is the documentation itself. For
example, I think we need a lot more overview docs than we have now.
Most of what we have now is doctest output. But in any case, I've
uploaded the current set of documentation to the Cheeseshop:
http://packages.python.org/mailman/docs/README.html
Volunteers are definitely wanted to help smooth out the build process,
theme the documentation to "Mailman style" and help fill out the
content.
(3) docs/ALPHA.txt says you need an unofficial branch of lazr.config ... which doesn't seem to exist:
It's a lie. Mailman 3 now uses the standard lazr.config package.
Documentation is updated. So bin/buildout will DTRT.
*sigh* I guess I'll just be a good little boy and get the PyPI package, but ... nah, I'll just go to bed and when I wake up I'll discover it was all a bad dream, right?
Yes, that's it! A bad dream. Check out
http://packages.python.org/mailman/docs/ALPHA.html
which should be much more helpful now.
what-can-this-strange-device-be?-ly y'rs, -Barry
participants (7)
-
Barry Warsaw -
Barry Warsaw -
Bernd Siggy Brentrup -
Mark Sapiro -
Patrick Ben Koetter -
Stefan Förster -
Stephen J. Turnbull