From Fedora Project Wiki
(Created page with "<!-- Self Contained or System Wide Change Proposal? Use this guide to determine to which category your proposed change belongs to. Self Contained Changes are: * changes to isolated/leaf package without the impact on other packages/rest of the distribution * limited scope changes without the impact on other packages/rest of the distribution * coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG System Wide Changes are: * cha...")
 
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<!-- Self Contained or System Wide Change Proposal?
Use this guide to determine to which category your proposed change belongs to.
Self Contained Changes are:
* changes to isolated/leaf package without the impact on other packages/rest of the distribution
* limited scope changes without the impact on other packages/rest of the distribution
* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
System Wide Changes are:
* changes that does not fit Self Contained Changes category touching
* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
* changing system defaults
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies). 
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
-->
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
= PHP 8.2 =
= PHP 8.2 =


Line 44: Line 22:
== Current status ==
== Current status ==


[[Category:ChangeReadyForWrangler]]
[[Category:ChangeAcceptedF38]]
<!-- 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 53: Line 31:
[[Category:SelfContainedChange]]
[[Category:SelfContainedChange]]


* Targeted release: [[Releases/38 | Fedora Linux 38 ]]  
* Targeted release: [[https://docs.fedoraproject.org/en-US/releases/f38/ | Fedora Linux 38 ]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 63: Line 41:
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
-->
-->
* FESCo issue:  
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GC5GGHVU72YQPSLDCGVDCOGDJVRQYRAD/ devel thread]
* Tracker bug:  
* FESCo issue: [https://pagure.io/fesco/issue/2875 #2875]
* Release notes tracker:  
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2132433 #2132433]
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/888 #888]


* An testing module is available in my [https://blog.remirepo.net/post/2022/09/02/PHP-on-the-road-to-the-8.2.0-release]
* An testing module is available in my [https://blog.remirepo.net/post/2022/09/02/PHP-on-the-road-to-the-8.2.0-release repository]
* List of [https://github.com/remicollet/remirepo/issues/206 extensions compatibility list]
* List of [https://github.com/remicollet/remirepo/issues/206 extensions compatibility list]
* [https://wiki.php.net/todo/php82 Upstream schedule for 8.2]
* [https://wiki.php.net/todo/php82 Upstream schedule for 8.2]


* Oct 5th: 8.2.0RC3 built in Rawhide, with mass rebuild of all extensions, see [https://bodhi.fedoraproject.org/updates/FEDORA-2022-69f3d6aa4a Bodhi update]
* Oct 11th: [https://bodhi.fedoraproject.org/updates/FEDORA-2022-ca089b5d7e 8.2.0RC4] built in Rawhide
* Dec 6th: [https://bodhi.fedoraproject.org/updates/FEDORA-2022-27bd55df90 8.2.0] built in Rawhide


== Detailed Description ==
== Detailed Description ==

Latest revision as of 11:08, 20 July 2023

PHP 8.2

Summary

Update the PHP stack in Fedora to the latest version 8.2.x

Owner

Current status

  • Oct 5th: 8.2.0RC3 built in Rawhide, with mass rebuild of all extensions, see Bodhi update
  • Oct 11th: 8.2.0RC4 built in Rawhide
  • Dec 6th: 8.2.0 built in Rawhide

Detailed Description

Update the PHP stack in Fedora to latest version 8.2.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)

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:
  • 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

Documentation

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/php82&oldid=683684"