According to https://fedoraproject.org/wiki/Changes/Python3.9#Important_dates_and_plan I'd like to include the final release of Python 3.9.0 in Fedora 33 GA. While the release should technically happen 1 day before the final freeze, from experience it might be slipped by couple days. There are not many changes anticipated between Python 3.9.0rc2 and final, except very important bugfixes. Such bugfixes could be delivered as 0-day update, but this is mostly about perception. I'd like to avoid shipping a release candidate in a final Fedora release. A temporary branch exists in upstream for changes between 3.9.0rc2 and final: https://github.com/python/cpython/tree/branch-v3.9.0 Today, there are no changes.
So... what does this mean: Should the branch from before the release be shippped as "3.9" in F33?
No. We would simply update to 3.9.0 final once it is released and put it in with a final freeze exception. https://www.python.org/dev/peps/pep-0596/ Expected: 3.9.0 final: Monday, 2020-10-05 https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html Final Freeze: Tue 2020-10-06 Final Release Public Availability (GA): Tue 2020-10-20
Oh, OK. I confused the final freeze with the final release. +1 for FE.
+1 FE
Nick, please vote in https://pagure.io/fedora-qa/blocker-review/issue/132
Marking as AcceptedFreezeException as per voting: https://pagure.io/fedora-qa/blocker-review/issue/132
https://src.fedoraproject.org/rpms/python3.9/pull-request/36
FEDORA-2020-e3cbc42959 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e3cbc42959
FEDORA-2020-e3cbc42959 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.