From Fedora Project Wiki
< Changes
(Announcing the Change proposal) |
|||
| Line 1: | Line 1: | ||
= PHP 8.3 = | = PHP 8.3 = | ||
{{Change_Proposal_Banner}} | |||
== Summary == | == Summary == | ||
| Line 22: | Line 25: | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeAnnounced]] | ||
<!-- 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 --> | ||
| Line 41: | Line 44: | ||
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 | ||
--> | --> | ||
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/ | * [https://discussion.fedoraproject.org/t/f40-change-proposal-php-8-3-self-contained/89611/1 Discussion Thread] | ||
* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/XCBFLJNE27V3DUTWSTWREXEBTEYWCEDE/ Announced] | |||
* FESCo issue: | * FESCo issue: | ||
* Tracker bug: | * Tracker bug: | ||
| Line 79: | Line 83: | ||
<!-- 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:[https://pagure.io/releng/issues #Releng issue number]<!-- 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 rebuid required? If a rel-eng ticket exists, add a link here. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. | ||
Revision as of 17:13, 11 September 2023
PHP 8.3
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
Update the PHP stack in Fedora to the latest version 8.3.x
Owner
- Name: Remi Collet and PHP SIG
- Email: remi at fedoraproject dot org
Current status
- Targeted release: [Fedora Linux 40 ]
- Last updated: 2023-09-11
- Discussion Thread
- Announced
- FESCo issue:
- Tracker bug:
- Release notes tracker:
- A testing SCL and a testing module are available in my repository
- List of extensions compatibility list
- Upstream schedule for 8.3
First RC is planed for August 31th, GA is planed for November 23th.
Detailed Description
Update the PHP stack in Fedora to latest version 8.3.x.
Fedora has a 6 months cycle, PHP a 1 year cycle, our common practice for some years:
- 2 Fedora cycles for each PHP minor release (exceptions below)
- 3 Fedora cycles for latest minor (e.g. 5.6 or 7.4) to give more time before next major
- 1 Fedora cycle for first major (e.g. 7.0 or 8.0)
Fedora 37 has PHP 8.1, Fedora 38 and 39 have PHP 8.2.
Benefit to Fedora
Provides the latest PHP version to developers and system administrators.
Scope
- Proposal owners: Check Koschei status. Test with latest version to ensure compatibility. Work with upstream on bug fixing. Needed mass rebuild (C extensions) done by change owner.
- Other developers: N/A (not a System Wide Change)
- Release engineering:#Releng issue number
- List of deliverables: 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
N/A (not a System Wide Change)
How To Test
- The PHP stack (extensions and libraries) are monitored by Koschei, see the Koschei PHP group
- install and play with your web applications
User Experience
Developers and system administrators will have the great benefit or running the latest PHP version.
Dependencies
All php-* packages (and some *-php)
Contingency Plan
- Contingency mechanism: Drop not compatible packages.
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product