From Fedora Project Wiki
(Remove not System Wide note)
Line 114: Line 114:


<!-- 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: (What to do?  Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency mechanism: Wait for 5.6.0RC1, so we'll, at least, ship a RC <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- 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: June <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release?: No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks release?: No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

Revision as of 06:41, 3 April 2014


PHP 5.6

Summary

Update the PHP stack to new version 5.6.

Owner

  • Name: Remi Collet
  • Email: remi @ fedora project DOT org
  • Release notes owner:

Current status

  • Targeted release: Fedora 21
  • Last updated: 2014-03-26
  • Tracker bug: <will be assigned by the Wrangler>

Upstream releases:

  • PHP 5.6.0alpha3 released Mar 6th 2014

Detailed Description

Important changes in this new version:

Security:

Language improvements:

New tool:

  • PHP debugger provided in the new php-dbg subpackage (phpdbg command)

Benefit to Fedora

Provides the latest upstream PHP version.

Scope

  • Proposal owners:

Mass rebuild of all C extensions (repoquery --whatrequires 'php(api)')

  • Other developers:

(pure) PHP extension owners: ensure compatibility, usually this is detected by running upstream test suite, when exists.

PHP webapp owners: test

  • Release engineering:

N/A.

  • Policies and guidelines:

N/A.

Upgrade/compatibility impact

This new version should maintains compatibility with version 5.5.x.

How To Test

  • test PHP web applications available in the repository

Fedora 19/20 users can use backported packages from remi-php56 repository.

User Experience

Web developer will get the latest upstream PHP version.

Dependencies

Mass rebuild need: from repoquery --whatrequires 'php(zend-abi)'

Known as not ready:

  • php-pecl-parsekit (mostly dead upstream)
  • php-xcache (actively maintained upstream)

Contingency Plan

According to upstream roadmap, 5.6.0 final should be released around June.

  • Contingency mechanism: Wait for 5.6.0RC1, so we'll, at least, ship a RC
  • Contingency deadline: June
  • Blocks release?: No
  • Blocks product?: No

Documentation

Upstream documentation: Migrating from PHP 5.5.x to PHP 5.6.x

Release Notes