From Fedora Project Wiki
Line 97: Line 97:
== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
* test PHP web applications available in the repository
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
A good "how to test" should answer these four questions:
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
N/A (not a System Wide Change)
== User Experience ==
== User Experience ==

Revision as of 09:57, 26 March 2014

Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.

PHP 5.6


Update the PHP stack to new version 5.6.


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

Detailed Description

Important changes in this new version:


Language improvements:

New tool:

Benefit to Fedora

Provides the latest upstream PHP version.


  • Proposal owners:

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

  • Other developers:

(pure) PHP extension owners: ensure compatibility, usually this is detect byt running upstream test suite.

PHP webapp owners: test

  • Release engineering:


  • Policies and guidelines: N/A (not a System Wide Change)


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

User Experience

Web developer will get the latest upstream PHP version.


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

  • 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 <-- Applicable for Changes that blocks specific product release/ -->


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

Release Notes