[Release management team communication] 3.8.10, the last regular bugfix release for the 3.8 series, is 1 week away
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/>.
- Ł
On 4/26/2021 4:18 PM, Łukasz Langa wrote:
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 ;-)
Perhaps 200 of those are IDLE issues and I don't expect to commit any to 3.8 (unless I get to a doc issue or two). I hope to get an important IDLE patch into 0b0, but this later, I will wait until after 3.9.5 to backport, for 3.9.6. (I want to first test it in personal daily use at least a couple of weeks before a production release.)
I'm personally rooting for https://github.com/python/cpython/pull/25274
<https://github.com/python/cpython/pull/25274> to get in.
To run on the new Mac hardware and OS version. I understand. You might make it more likely if you were willing, if necessary, to do an emergency release to fix or revert if needed.
-- TJR
participants (2)
-
Terry Reedy -
Łukasz Langa