-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin points out that in the past, as part of the release process,
we've built separate downloadable documentation.
Do we still want to do that for Python 2.6 and 3.0, and if so, how do
we go about doing that? I have this feeling that building the
documentation is much different now than in the past, and I don't
really have a good feel for how it's done now.
If you think we should release separate downloadable documentation and
can help integrate that into the release project, you just might be a
Documentation Expert <wink>. Please let me know if you can help.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSNOLBnEjvBPtnXfVAQIQnAQAm6thEThGufep6hzHxBwAN8MTsLb9jxsu
Z8GAtX1bdMNOrJczYpU6by0oXPLR2pupnGV1YrAyQyoqpk+K7W8by5Qtg8+ZZcYH
GerkqMVtNYn2zY1HhKigivp2JvlqIidRc5D36XS2EJixhZEPcOQDVm34THNQyRJT
QasCQwdSAHI=
=MbMY
-----END PGP SIGNATURE-----
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
