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 is...")
 
No edit summary
 
(9 intermediate revisions by 2 users not shown)
Line 44: Line 44:
== Current status ==
== Current status ==


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


* Targeted release: [[Releases/36 | Fedora 36 ]]  
* Targeted release: [[Releases/36 | Fedora Linux 36 ]]  
* 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 63:
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:  
* FESCo issue: [https://pagure.io/fesco/issue/2674 #2674]
* Tracker bug:  
* Tracker bug: [https://bugzilla.redhat.com/2014559 #2014559]
* Release notes tracker:  
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/744 #744]


* An testing module is available in my [https://blog.remirepo.net/post/2021/09/02/PHP-on-the-road-to-the-8.1.0-release]
* An testing module is available in my [https://blog.remirepo.net/post/2021/09/02/PHP-on-the-road-to-the-8.1.0-release]
Line 71: Line 71:
* [https://wiki.php.net/todo/php81 Upstream schedule for 8.1]
* [https://wiki.php.net/todo/php81 Upstream schedule for 8.1]


* Sep 30th 2020 PHP 8.1.0RC1 was released
* Oct 30th 2021 PHP 8.1.0RC5 was build in rawhide, and most extensions rebuilt, see [https://bodhi.fedoraproject.org/updates/FEDORA-2021-610b3547a3 Bodhi update]
* Nov 10th 2021 PHP 8.1.0RC6 was build in rawhide, see [https://bodhi.fedoraproject.org/updates/FEDORA-2021-774d2db4c9 Bodhi update]
* Nov 25th 2021 '''PHP 8.1.0''' GA is released and built in rawhide, see [https://bodhi.fedoraproject.org/updates/FEDORA-2021-ef9445f672 Bodhi update]


== Detailed Description ==
== Detailed Description ==
Line 77: Line 79:
Update the PHP stack in Fedora to latest version 8.1.x.
Update the PHP stack in Fedora to latest version 8.1.x.


Fedora have a 6 months cycle, PHP and a 1 year, common practice for some years
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)
* 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
* 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)
* 1 Fedora cycle for first major (e.g. 7.0 or 8.0)


== Benefit to Fedora ==
== Benefit to Fedora ==

Latest revision as of 19:02, 25 November 2021


PHP 8.1

Summary

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

Owner

Current status

  • Oct 30th 2021 PHP 8.1.0RC5 was build in rawhide, and most extensions rebuilt, see Bodhi update
  • Nov 10th 2021 PHP 8.1.0RC6 was build in rawhide, see Bodhi update
  • Nov 25th 2021 PHP 8.1.0 GA is released and built in rawhide, see Bodhi update

Detailed Description

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