From Fedora Project Wiki
No edit summary
Line 107: Line 107:


== Benefit to Fedora ==
== Benefit to Fedora ==
<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
 
Fedora aims to showcase the latest in free and open-source software - we should have the most recent release of Python 3. Packages in Fedora can use the new features from 3.11.
      Be sure to include the following areas if relevant:
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
      If this is a major capability update, what has changed?
          For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
      If this is a new functionality, what capabilities does it bring?
          For example: This change allows package upgrades to be performed automatically and rolled-back at will.
      Does this improve some specific package or set of packages?
          For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
      Does this improve specific Spins or Editions?
          For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
      Does this make the distribution more efficient?
          For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
      Is this an improvement to maintainer processes?
          For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
      Is this an improvement targeted as specific contributors?
          For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.


    When a Change has multiple benefits, it's better to list them all.
There's also a benefit to the larger Python ecosystem: by building Fedora's packages against 3.0 while it's still in development, we can catch critical bugs before the final 3.11.0 release.
 
    Consider these Change pages from previous editions as inspiration:
    https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
    https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
    https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
    https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
    https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
-->


== Scope ==
== Scope ==

Revision as of 15:11, 29 September 2021


Python 3.11

Summary

Update the Python stack in Fedora from Python 3.10 to Python 3.11, the newest major release of the Python programming language.

Owner


Current status

  • Targeted release: Fedora Linux 37
  • Last updated: 2021-09-29
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

We would like to upgrade Python to 3.11 in Fedora 37 thus we are proposing this plan early.

See the upstream notes at Features for 3.11 and What's new in 3.11.

Important dates and plan

  • 2021-05-03: Python 3.11 development begins
  • 2021-10-04: Python 3.11.0 alpha 1
    • Package it as Package-x-generic-16.pngpython3.11 for testing purposes
    • Start the bootstrap procedure in Copr
    • Do a mass rebuild against every future release in Copr
  • 2021-11-02: Python 3.11.0 alpha 2
  • 2021-12-06: Python 3.11.0 alpha 3
  • 2022-01-03: Python 3.11.0 alpha 4
  • 2022-02-02: Python 3.11.0 alpha 5
  • [2022-02-09]: Branch Fedora 36, Rawhide becomes future Fedora 37
    • The earliest point when we can start rebuilding in Koji side-tag
  • 2022-02-28: Python 3.11.0 alpha 6
  • 2022-04-05: Python 3.11.0 alpha 7
  • 2022-05-06: Python 3.11.0 beta 1
    • No new features beyond this point
  • 2022-05-30: Python 3.10.0 beta 2
    • The ideal point when we can start rebuilding in Koji
  • 2022-06-06: Expected side tag-merge (optimistic)
  • 2022-06-16: Python 3.11.0 beta 3
  • 2022-06-24: Expected side tag-merge (realistic)
  • 2022-07-09: Python 3.11.0 beta 4
  • 2022-07-18: Expected side tag-merge (pessimistic)
  • [2022-07-21]: Fedora 37 Mass Rebuild
    • The mass rebuild happens with the fourth beta. We might need to rebuild Python packages later in exceptional case.
    • If the Koji side-tag is not merged yet at this point, we defer the change to Fedora 38.
  • 2022-08-01: Python 3.11.0 candidate 1
    • This serves as "final" for our purposes.
  • [2022-08-10]: Branch Fedora 37, Rawhide becomes future Fedora 38
  • [2022-08-10]: Fedora 37 Change Checkpoint: Completion deadline (testable)
  • [2022-08-24]: Fedora Beta Freeze
    • If rebuild with 3.11.0rc1 is needed, we should strive to do it before the freeze - there is a window of 3 weeks.
  • 2022-09-05: Python 3.11.0 candidate 2
  • [2022-09-19]: Fedora 37 Beta Release (Preferred Target)
    • Beta will likely be released with 3.11.0rc2.
  • [2022-09-21]: Fedora 37 Beta Target date #1
  • 2022-10-03: Python 3.11.0 final
  • [2022-10-05]: Fedora 37 Final Freeze
    • We'll update to 3.11.0 final using a freeze exception.
  • [2022-10-19]: Fedora 37 Preferred Final Target date
  • [2022-10-26]: Fedora 37 Final Target date #1


(From Python 3.11 Release Schedule and Fedora 37 Release Schedule (dates in [] are based on Fedora 35 Release Schedule and will be adjusted accordingly when schedule for Fedora 37 is available).)

The schedule might appear somewhat tight for Fedora 37, but Python's annual release cycle was adapted for Fedora and this worked fine since Python 3.9 and Fedora 33. It is now common that Python is upgraded on a similar schedule in every odd-numbered Fedora release.

Note that upstream's "release candidates" are frozen except for blocker bugs. Since we can and will backport blocker fixes between Fedora and upstream, we essentially treat the Release Candidate as the final release.

Notes from the previous upgrade

There are notes from the previous upgrade available, so this upgrade may go smoother: SIGs/Python/UpgradingPython

Benefit to Fedora

Fedora aims to showcase the latest in free and open-source software - we should have the most recent release of Python 3. Packages in Fedora can use the new features from 3.11.

There's also a benefit to the larger Python ecosystem: by building Fedora's packages against 3.0 while it's still in development, we can catch critical bugs before the final 3.11.0 release.

Scope

  • Proposal owners:
  • Other developers:
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

How To Test

User Experience

Dependencies

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No


Documentation

N/A (not a System Wide Change)

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Python3.11&oldid=626137"