From Fedora Project Wiki
(Scope)
Line 77: Line 77:
  
 
* Proposal owners:
 
* Proposal owners:
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+
Mass rebuild of all C extensions (repoquery --whatrequires 'php(api)')
  
* Other developers: PHP extensions and PHP webapp owner <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
  
* Release engineering: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
(pure) PHP extension owners: ensure compatibility, usually this is detect byt running upstream test suite.
 +
 
 +
PHP webapp owners: test
 +
 
 +
* Release engineering:   <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
 +
N/A.
  
 
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
 
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
 +
N/A.
  
 
== Upgrade/compatibility impact ==
 
== Upgrade/compatibility impact ==

Revision as of 09:01, 26 March 2014

Important.png
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 detect byt running upstream test suite.

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

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