[Mailman-Developers] Mailman 2.1.16 release.

[Mark Sapiro]

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.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Version.py.patch
Type: text/x-diff
Size: 593 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20131016/ebcb3041/attachment-0001.patch>