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