I am pleased to announce the first release candidate for Mailman 2.1.16.

Python 2.4 is the minimum supported, but Python 2.7 is recommended.

This release has a few new features and several bug fixed as detailed in the attached README.

Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, please see:

http://www.list.org http://www.gnu.org/software/mailman http://mailman.sourceforge.net/

Mailman 2.1.16rc1 can be downloaded from

https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/

I anticipate that the 2.1.16 final release will be in early September. Bugs found between now and then will be fixed if possible, but I hope that most if not all changes between now and then will be i18n updates. Please send any updates to the templates and/or message catalogs in the 2.1.16rc1 release directly to me no later than 1 Sept 2013.

I am pleased to announce the third release candidate for Mailman 2.1.16.

Python 2.4 is the minimum supported, but Python 2.7 is recommended.

This release has a few new features and several bug fixed as detailed in the attached README.

Differences from the second candidate are the renaming of the author_is_list feature to from_is_list to more accurately describe what it does. This feature has also been extended to provide the option of leaving the original message intact and wrapping it in an outer part with Content-Type: message/rfc822.

The from_is_list feature is considered experimental and subject to change in future releases. It is being released now as a "candidate" to allow some exposure before the final 2.1.16 release which should occur in October.

Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, please see:

http://www.list.org http://www.gnu.org/software/mailman http://mailman.sourceforge.net/

Mailman 2.1.16rc3 can be downloaded from

https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/

I anticipate that the 2.1.16 final release will be in Mid October. Bugs found between now and then will be fixed if possible, but I hope that most if not all changes between now and then will be i18n updates. Please send any updates to the templates and/or message catalogs in the 2.1.16rc3 release directly to me no later than 15 Oct 2013.

On Oct 16, 2013, at 08:12 AM, Mark Sapiro wrote:

I am pleased to announce the final release for Mailman 2.1.16.

Congratulations Mark!

-Barry

On 10/16/2013 08:31 AM, Andrew Hodgson wrote:

Thanks for the good release as always. Sorry to ask this, but will your Htdig integration patch for 2.1.15 also work on 2.1.16, or are the differences too great for the patch to apply successfully?

The patch for 2.1.16 is now there at http://www.msapiro.net/mm/index_htdig.patch.2.1.16. There were only a few minor line number changes between that and the 2.1.15 patch.

On 10/16/2013 10:44 AM, Andrew Hodgson wrote:

Thanks for this. All working fine this end. Only thing I can see is the version text still says that it is running RC3.

and On 10/16/2013 07:21 PM, Christopher Schulte wrote:

Hi Mark, I pulled down

http://ftp.gnu.org/gnu/mailman/mailman-2.1.16.tgz

and my list web interface shows version 2.1.16rc3. Maybe someone forgot to bump Version.py ?

Actually, it's a bit more tangled than that. For those keeping score at home, I have a script that I use to 1) bump the version 2) tag the release and 3) package the tarball. The issue is step 1) bumps the version, but doesn't commit, then step 2) tags the latest (prior) commit and then commits, and step 3) packages the tagged version which doesn't have the bump. Sometimes I remember to commit between steps 1) and 2), and sometimes I don't.

I have updated the script to commit after the bump in step 1) which will avoid this in the future I hope.

I have replaced the tarballs at the download sites:

https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/

with ones that have the correct version. This is the only difference between the new tarballs and the prior ones. If you downloaded one earlier and care about the displayed version, you can either download a new one or apply the attached Version.py.patch.