Line 123: | Line 123: | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: | * Contingency mechanism: Drop not compatible packages. | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> |
Revision as of 11:52, 11 October 2016
PHP 7.1
Summary
Update the PHP stack in Fedora to latest version 7.1.x
Owner
- Name: Remi Collet and PHP SIG
- Email: remi at fedoraproject dot org
- Release notes owner:
Current status
- Targeted release: Fedora 26
- Last updated: 2016-10-11
- Tracker bug: <will be assigned by the Wrangler>
Most of the work is done in my personal repository, see php71 repository for Fedora 24
All extensions compatible with PHP 7.0 are ready for PHP 7.1
Detailed Description
Update the PHP stack in Fedora to latest version 7.1.x.
- PHP 7.1.0RC3 was released Sep 29th
- PHP 7.1.0 is planed for end of year.
Compatibility for PHP code is very good.
PHP 7.1 is the first compatible version with OpenSSL 1.1.
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.
- Other developers: N/A (not a System Wide Change)
- Release engineering: needed mass rebuild (C extensions) done by change owner.
- 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