From Fedora Project Wiki
No edit summary
 
(25 intermediate revisions by 3 users not shown)
Line 34: Line 34:
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: remi at fedoraproject dot org
* Email: remi at fedoraproject dot org
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
* Release notes ticket: [https://pagure.io/fedora-docs/release-notes/issue/88 #88]
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
Line 44: Line 44:


== Current status ==
== Current status ==
* Targeted release: [[Releases/27 | Fedora 27 ]]  
* Targeted release: [[Releases/28 | Fedora 28 ]]  
* 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 54: Line 54:
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=1474939 #1474939]


Most of the work is done in my personal repository
* PHP '''7.2.0RC3''' have been imported in Rawhide on October 3rd, 2017
 
* PHP '''7.2.0RC4''' have been imported in Rawhide on October 10th
Most of extensions compatible with PHP 7.1 are ready for PHP 7.2
* PHP '''7.2.0RC5''' have been imported in Rawhide on October 25th
 
* PHP '''7.2.0RC6''' have been imported in Rawhide on November 7th
* mcrypt extension is dropped from PHP but can be provided as a pecl extension, if really wanted.
* PHP '''7.2.0 GA''' have been released and imported in Rawhide on November 30th
* all dependent packages have been rebuilt
* php-mcrypt is dropped from PHP, php-pecl-mcrypt is available for legacy applications
* On November 14th everything is "green" on Koschei


== Detailed Description ==
== Detailed Description ==
Line 79: Line 82:


== Scope ==
== Scope ==
* Proposal owners: Check Koschei status. Test with latest version to ensure compatibility. Work with upstream on bug fixing.
* 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.


<!-- 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 86: Line 89:
<!-- 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: needed mass rebuild (C extensions) done by change owner.  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: [https://pagure.io/releng/issue/6846 RelEng ticket #6846] <!-- 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.  
Line 132: Line 135:
== Documentation ==
== Documentation ==


<!-- * [http://php.net/manual/en/migration71.php http://php.net/manual/en/migration71.php] -->
*[http://www.php.net/ChangeLog-7.php#7.2.0 CHANGELOG]
* [https://raw.githubusercontent.com/php/php-src/master/UPGRADING UPGRADING]
* [http://php.net/manual/en/migration72.php Migrating from PHP 7.1.x to PHP 7.2.x]
* [https://raw.githubusercontent.com/php/php-src/master/UPGRADING.INTERNALS UPGRADING.INTERNALS]
* [https://raw.githubusercontent.com/php/php-src/PHP-7.2/UPGRADING UPGRADING]
* [https://raw.githubusercontent.com/php/php-src/PHP-7.2/UPGRADING.INTERNALS UPGRADING.INTERNALS]


== Release Notes ==
== Release Notes ==
Line 150: Line 154:


<!-- Select proper category, default is Self Contained Change -->
<!-- Select proper category, default is Self Contained Change -->
[[Category:ChangeReadyForWrangler]]
[[Category:ChangeAcceptedF28]]
<!-- [[Category:SystemWideChange]] -->
[[Category:SelfContainedChange]]

Latest revision as of 14:49, 2 March 2018


PHP 7.2

Summary

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

Owner

Current status

  • PHP 7.2.0RC3 have been imported in Rawhide on October 3rd, 2017
  • PHP 7.2.0RC4 have been imported in Rawhide on October 10th
  • PHP 7.2.0RC5 have been imported in Rawhide on October 25th
  • PHP 7.2.0RC6 have been imported in Rawhide on November 7th
  • PHP 7.2.0 GA have been released and imported in Rawhide on November 30th
  • all dependent packages have been rebuilt
  • php-mcrypt is dropped from PHP, php-pecl-mcrypt is available for legacy applications
  • On November 14th everything is "green" on Koschei

Detailed Description

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

  • PHP 7.2.0 is planed for end of year, which seems compatible with Fedora roadmap.

Compatibility for PHP code is very good.


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