Hi there,
one week from now I will be marking the 3.8 branch as "security fixes only". I 
still see activity on the branch, and there's been a bunch of open pull 
requests. I reviewed and merged what I could, closed a few stale ones that had 
outstanding failing tests, and there's still two left which I pinged.

I do realize that stars aligned and we will be releasing this last bugfix 
version of 3.8 at the same time as 3.9.5, and more importantly 3.10.0 beta 1. 
So there might still be some backport pull requests coming my way for 3.8. This 
is all good and expected, just be a little conservative whether it makes sense 
to backport a particular change. While there's still 2200 open issues on BPO 
listing 3.8 as one of the affected versions, I hope we won't be seeing that 
many PRs this week ;-)

I'm personally rooting for https://github.com/python/cpython/pull/25274 
<https://github.com/python/cpython/pull/25274> to get in.

In any case, on Monday, May 3rd at 12pm CEST I will be cutting the 3.8.10 
release. Any regular bugfix not merged and buildbot-tested by then will be 
omitted. If you need to block this release for any reason, use the BPO "release 
blocker" status and mark 3.8 as an affected version.

3.9.5 being less urgent will be made on the same day after 3.8.10 is up on 
python.org <http://python.org/>.

- Ł
_______________________________________________
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/W5TUMGZXMO3GO6NXDWSSLQQUEUKM3V4K/
Code of Conduct: https://www.python.org/psf/codeofconduct/

Reply via email to