< Changes
No edit summary |
|||
| Line 1: | Line 1: | ||
<!-- Self Contained or System Wide Change Proposal? | <!-- Self Contained or System Wide Change Proposal? | ||
Use this guide to determine to which category your proposed change belongs to. | Use this guide to determine to which category your proposed change belongs to. | ||
| Line 171: | Line 169: | ||
<!-- Select proper category, default is Self Contained Change --> | <!-- Select proper category, default is Self Contained Change --> | ||
[[Category:SelfContainedChange]] | <!-- [[Category:SelfContainedChange]] --> | ||
[[Category:SystemWideChange]] | |||
Revision as of 09:16, 14 June 2016
PHP 7.0
Summary
Update the PHP stack in Fedora to latest version 7.0.x
Owner
- Name: Remi Collet
- Email: remi at fedoraproject dot org
- Release notes owner:
Current status
- Targeted release: Fedora 25
- Last updated: 2016-06-14
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Update the PHP stack in Fedora to latest version 7.0.x, which brings a big performance improvement.
- PHP 7.0.0 was released in December 2015.
- PHP 7.1.0 is planed for end of year, but is probably not compatible with our Schedule, will probably be a Fedora 26 feature
Compatibility for PHP code is very good, while internal API have big changes, implying a major rewrite of C extensions.
See documentation :
Benefit to Fedora
Provides the latest PHP version to developers and system administrators.
Some other distributions already provides this version, upgrade have been differed in Fedora to give time to projects using PHP to fix compatibility.
This will be an opportunity to clean (remove) old packages, not compatible and unmaintained upstream.
Scope
- Proposal owners: PHP SIG
- Other developers: all PHP package owners
- Release engineering: N/A (not a System Wide Change)
- 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
N/A (not a System Wide Change)
User Experience
N/A (not a System Wide Change)
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)