From Fedora Project Wiki
Line 108: Line 108:


== Contingency Plan ==
== Contingency Plan ==
According to upstream roadmap, 5.6.0 final should be released around June.
<!-- 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: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Line 113: Line 115:
* 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 -->
<!-- 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? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks release?: No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <-- Applicable for Changes that blocks specific product release/Fedora.next -->
* Blocks product?: No <-- Applicable for Changes that blocks specific product release/Fedora.next -->


== Documentation ==
== Documentation ==

Revision as of 10:01, 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

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>

Detailed Description

Important changes in this new version:

Security:

Language improvements:

New tool:

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 (not a System Wide Change)

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

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: (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?: No
  • Blocks product?: No <-- Applicable for Changes that blocks specific product release/Fedora.next -->

Documentation

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

Release Notes