[Python-Dev] [python-committers] Should I make a 3.4.7rc1 next weekend? (original) (raw)
Victor Stinner victor.stinner at gmail.com
Wed Jul 12 09🔞42 EDT 2017
- Previous message (by thread): [Python-Dev] Should I make a 3.4.7rc1 next weekend?
- Next message (by thread): [Python-Dev] Announcing the schedule for 3.4.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I would love to have a new 3.4 release including all security fixes, sure! It would reduce the number of known vulnerability in Python 3.4:
http://python-security.readthedocs.io/vulnerabilities.html
2017-07-12 15:09 GMT+02:00 Larry Hastings <larry at hastings.org>:
After a flurry of accepted PRs, I have now accrued about ten fresh security fixes in the 3.4 branch. (Mostly from Victor, but also Serhiy, and one from Barry--thanks everyone!) There are now no outstanding security fix PRs against 3.4.
Thanks for merging them ;-)
I would like to see my "[3.4] Backport CI config from master" PR merged into 3.4 to get at least a check from Travis and AppVeyor that there is no major regression on Linux and Windows: https://github.com/python/cpython/pull/2475
If I recall correctly, it would be the first time that we have a CI for a branch in security-fix only mode, no?
Victor
- Previous message (by thread): [Python-Dev] Should I make a 3.4.7rc1 next weekend?
- Next message (by thread): [Python-Dev] Announcing the schedule for 3.4.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]