Churchyard (talk | contribs) m (add mass rebuild date) |
(Two new paragraphs, and "python 3" → "Python" in the summary) |
||
| Line 24: | Line 24: | ||
== Summary == | == Summary == | ||
Update the Python | Update the Python stack in Fedora from Python 3.7 to Python 3.8. | ||
== Owner == | == Owner == | ||
| Line 80: | Line 80: | ||
* 2019-10-16 expected earliest Fedora 31 final freeze | * 2019-10-16 expected earliest Fedora 31 final freeze | ||
* 2019-10-20 Python 3.8.0 final | * 2019-10-20 Python 3.8.0 final | ||
** gets in with an pre approved exception | ** gets in with an pre-approved exception | ||
(From [https://www.python.org/dev/peps/pep-0569/#schedule Python 3.8 Release Schedule] and [[Releases/31/Schedule|Fedora 31 Release Schedule]].) | (From [https://www.python.org/dev/peps/pep-0569/#schedule Python 3.8 Release Schedule] and [[Releases/31/Schedule|Fedora 31 Release Schedule]].) | ||
The schedule is '''very tight''', but the Fedora dates are the earliest expectations. So we propose this early and the Fedora schedule might get adjusted. | The schedule is '''very tight''', but the Fedora dates are the earliest expectations. So we propose this early and the Fedora schedule might get adjusted. | ||
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 === | === Notes from the previous upgrade === | ||
| Line 94: | Line 96: | ||
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.8. | 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.8. | ||
<!-- 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?--> | <!-- 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?--> | ||
There's also a benefit to the larger Python ecosystem: by building Fedora's packages against 3.8 while it's still in development, we can catch critical bugs before the final 3.8.0 release. | |||
== Scope == | == Scope == | ||
Revision as of 09:03, 6 February 2019
Python 3.8
Summary
Update the Python stack in Fedora from Python 3.7 to Python 3.8.
Owner
- Name: Miro Hrončok
- Email: python-maint@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 31
- Last updated: 2019-02-06
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
We want to upgrade Python to 3.8 in Fedora 31 and we propose this plan early.
See the upstream notes at Features for 3.8 and What's new in 3.8.
Important dates and plan
- 2019-02-03 Python 3.8.0 alpha 1
- we package it as
python38 - we start bootstrapping against it in Copr
- we mass rebuild against every future release in Copr
- we package it as
- 2019-05-26 Python 3.8.0 beta 1
- if Copr was good, we push to rawhide and bootstrap + mass rebuild in a side tag
- , 2019-06-23 Python 3.8.0 beta 2
- if side tag was good, we merge it to Fedora at this point
- 2019-07-30 expected earliest Fedora 31 mass rebuild
- 2019-09-05 expected earliest Fedora 31 beta freeze
- everything should be well tested on beta 1 to 4
- 2019-09-29 Python 3.8.0 candidate 1
- (we block Fedora release before we have this)
- 2019-10-16 expected earliest Fedora 31 final freeze
- 2019-10-20 Python 3.8.0 final
- gets in with an pre-approved exception
(From Python 3.8 Release Schedule and Fedora 31 Release Schedule.)
The schedule is very tight, but the Fedora dates are the earliest expectations. So we propose this early and the Fedora schedule might get adjusted.
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.8.
There's also a benefit to the larger Python ecosystem: by building Fedora's packages against 3.8 while it's still in development, we can catch critical bugs before the final 3.8.0 release.
Scope
We will coordinate the work in a side tag and merge when ready.
- Proposal owners:
- Introduce
- Prep stuff in Copr as explained in description.
- Retire
- Update
- Mass rebuild all the packages that BR
- Mass rebuild all the packages that BR
- Reintroduce
- Introduce
- Other developers: Maintainers of packages that fail to rebuild during the rebuilds will be asked, using e-mail and bugzilla, to fix or remove their packages from the distribution. If any issues appear, they should be solvable either by communicating with upstreams first and/or applying downstream patches. Also the package maintainers should have a look at: Porting to Python 3.8. And python-maint team will be available to help with fixing issues.
- Fedora QA: Based on some troubles with the change to 3.6, we'd like to have an ack from QA before we merge the side tag. We'd also like QA to approve this change.
- Release engineering: #8092 A targeted rebuild for all python packages will be required, before the mass rebuild.
- List of deliverables: nope
- Policies and guidelines: nope
- Trademark approval: nope
Upgrade/compatibility impact
All the packages that depend on Python 3 must be rebuilt. User written Python 3 scripts/applications may require a small amount of porting, but mostly Python 3.7 is forward compatible with Python 3.8.
How To Test
Interested testers do not need special hardware. If you have a favorite Python 3 script, module, or application, please test it with Python 3.8 and verify that it still works as you expect. You can test it using 
python38
Once the change is in place, test if you favorite Python apps are working as they were before. File bugzillas if they don't.
User Experience
Regular distro users shouldn't notice any change in system behavior other than the Python 3 interpreter will be in version 3.8.
Dependencies
~2700 packages depend on
Contingency Plan
- Contingency mechanism: Do not merge the side tag with rawhide. If the side tag has been merged and issues arise, that will justify a downgrade, then use an epoch tag to revert to 3.7 version (never needed before)
- Contingency deadline: TBD
- Blocks release? Yes, we'd like to block Fedora 31 release on at least 3.8.0 rc 1
- Blocks product? See above
Documentation
Release Notes
- Release Notes tracking: #XXX