From Fedora Project Wiki
< Changes
Churchyard (talk | contribs) (Initial change proposal) |
m (Add trackers) |
||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 25: | Line 25: | ||
Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". --> | Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". --> | ||
The {{package|python26}} package will be retired without replacement from [[Releases/33|Fedora 33]]. Python 2.6 | The {{package|python26}} package will be retired without replacement from [[Releases/33|Fedora 33]]. Python 2.6 has been End of Life since October 2013 and was kept around only to test software targeting RHEL/EPEL 6. The removal is aligned with EPEL 6 EOL. | ||
== Owner == | == Owner == | ||
| Line 53: | Line 53: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1795315 #1795315] | ||
* Release notes tracker: | * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/440 #440] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 62: | Line 62: | ||
The {{package|python26}} package with the Python interpreter in version 2.6 is kept in Fedora only to make it possible for Fedora users to test their software against the Python version shipped in RHEL 6. | The {{package|python26}} package with the Python interpreter in version 2.6 is kept in Fedora only to make it possible for Fedora users to test their software against the Python version shipped in RHEL 6. | ||
[[EPEL|The EPEL 6 End of Life is planned for 2020-11]]. This roughly corresponds with [https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html Fedora 33 release date]. | [[EPEL|The EPEL 6 End of Life is planned for 2020-11]]. This roughly corresponds with the [https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html Fedora 33 release date]. Hence, we decided to retire (completely remove) {{package|python26}} from Fedora 33, before it gets released. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 95: | Line 93: | ||
https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack) | https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack) | ||
--> | --> | ||
The maintenance of Python 2.6 was getting harder and harder every year. The support for Python 2.6 has disappeared from virtualenv, tox. {{package|python26}} cannot be built against the new OpenSSL versions, etc. | |||
There is no direct benefit here, except that we don't want to maintain it anymore and we don't think it's a good idea either. | |||
Consider this change proposal a louder orphaning, except that we will continue to maintain the package in older released and supported Fedoras (31 and 32). If you wish to continue maintaining Python 2.6 in Fedora, please [[SIGs/Python|speak to us]] first. | |||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: Retire {{package|python26}}. Obsolete it from {{package|fedora-obsolete-packages}} if it causes troubles on upgrades. Make sure no Fedora package depends on it in any way (incl. weak dependencies). | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
| Line 103: | Line 107: | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Release engineering: | * Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
| Line 117: | Line 121: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
The package will no longer be available from the repositories, but it may remain on existing installations. If it causes troubles on upgrade, it needs to be obsoleted. | |||
== How To Test == | == How To Test == | ||
| Line 148: | Line 152: | ||
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system. | - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system. | ||
--> | --> | ||
No more Python 2.6 to test user software on. | |||
== Dependencies == | == Dependencies == | ||
| Line 178: | Line 184: | ||
--> | --> | ||
[[Category: | [[Category:ChangeAcceptedF33]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 16:49, 27 January 2020
Retire python26
Summary
The 
python26
Owner
- Name: Miro Hrončok
- Email: mhroncok@redhat.com
Current status
- Targeted release: Fedora 33
- Last updated: 2020-01-27
- Tracker bug: #1795315
- Release notes tracker: #440
Detailed Description
The
The EPEL 6 End of Life is planned for 2020-11. This roughly corresponds with the Fedora 33 release date. Hence, we decided to retire (completely remove)
Benefit to Fedora
The maintenance of Python 2.6 was getting harder and harder every year. The support for Python 2.6 has disappeared from virtualenv, tox.
There is no direct benefit here, except that we don't want to maintain it anymore and we don't think it's a good idea either.
Consider this change proposal a louder orphaning, except that we will continue to maintain the package in older released and supported Fedoras (31 and 32). If you wish to continue maintaining Python 2.6 in Fedora, please speak to us first.
Scope
- Proposal owners: Retire
python26
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
The package will no longer be available from the repositories, but it may remain on existing installations. If it causes troubles on upgrade, it needs to be obsoleted.
How To Test
N/A (not a System Wide Change)
User Experience
No more Python 2.6 to test user software on.
Dependencies
N/A (not a System Wide Change)
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
- Blocks product? product
Documentation
N/A (not a System Wide Change)