.
.
.
I've clarified that first paragraph in the UPGRADING file, although because of SF CVS unavailability at the moment, I can't check in the change. Here's what it now reads:
For the most part, upgrading Mailman entails installing the latest version over the existing version. Usually, you can unpack the new release, run 'configure' with the same options you used in your previous install, and then do a 'make install'. However, there are some changes that may need to be taken care of manually.
Does that work for you?
Looks good to me. Thanks.
> 2. The file refers to > <http://mail.python.org/pipermail/mailman-users/2000-September/006826 > .html>. AFAICT that message is the wrong one. It doesn't relate to > upgrading, and isn't from the person referenced, and its four years > old.
Documentation bug. Barry?
I think the note there is a red herring now. Newer versions do a better job of migrating the template files from older versions, so I've simply removed that sections from the file.
Cheers, -Barry
cheers!
-- Ian Eiloart Servers Team Sussex University ITS
------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
