Re: [Fetchmail-users] fetchmail-6.4.0 release candidate #4 - please translate to your language, and test!

[Jerry <je...@se...>]

On Mon, 2 Sep 2019 19:27:45 +0200, Matthias Andree stated:
>Greetings,
>
>I have released fetchmail-6.4.0.rc4, it is available from
>sourceforge.net, see:
><https://sourceforge.net/projects/fetchmail/files/branch_6.4/>
>
>Since rc3,
>* several translation updates were merged,
>* several consistency issues in documentation and configuration were
>fixed,
>* comparing the 6.4.x branch with the 7.x.x branch, a few missed bug
>fixes and
>  safety nets were backported. This is hidden under the "Align with
> legacy_6x" label.
>
>These are non-translation updates since rc3:
>* c83898bf 2019-08-25 | Mention MDA single-quote fix safety check.
>[Matthias Andree]
>* e0e7a74b 2019-08-25 | Align with legacy_6x. [Matthias Andree]
>* 5256f612 2011-06-16 | mimedecode: Fix multipart/mixed detection.
>[Matthias Andree]
>* 525a4c43 2019-08-25 | Drop #ifdef HAVE_GETCWD, there never was a
>formal configure check. [Matthias Andree]
>* 6928f65f 2019-08-25 | fetchmail.man: fix typo spotted by lintian
>[Nicolas Boulenguez]
>* c8e26099 2019-08-25 | contrib/fetchmail-mode.el: run
>fetchmail-mode-hook after other settings [Kevin Ryde]
>* 51ea9ddc 2019-08-24 | Do not reference m4/gethostbyname_r.m4, we
>don't ship it any more. [Matthias Andree]
>* 7c7279e4 2019-08-24 | Remove crypt() check, we don't use it.
>[Matthias Andree]
>* e4f511bb 2019-08-24 | Require Python 2.3 (2.0 is no longer
>sufficient). [Matthias Andree]
>
>I have mailed the URL of the tarball to the translation project, 
>PLEASE DO TRANSLATE (and if you need more than a few days, let me know)
>
>I solicit thorough testing, I plan to not hold off on the release much
>longer, no matter what the TODO.txt says.  We need to get the SSL
>changes and other important fixes out the door, and unless serious
>bugs are found, this is slated to become v6.4.0 in September.
>
>Happy fetches,
>Matthias
>


I assume that a version of Python newer than 2.3 (July 29, 2003) will
work. Wouldn't it be better to at least require at least Python 3.0.0
(Dec. 3, 2008)?

-- 
Jerry