Latest revision as of 13:01, 28 August 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: Petr Bokoc pbokoc at redhat dot com

Current status

Targeted release: Fedora 21
Last updated: 2014-06-19
Tracker bug: #1089323

Upstream releases:

PHP 5.6.0alpha3 released Mar 6th 2014
PHP 5.6.0beta1 released Apr 11th 2014
PHP 5.6.0beta2 released May 2nd 2014
PHP 5.6.0beta3 released May 15th 2014
PHP 5.6.0beta6 released Jun 6th 2014 (last before RC)
PHP 5.6.0RC1 released Jun 19th 2014
PHP 5.6.0RC2 released Jul 3rd 2014
PHP 5.6.0RC3 released Jul 31th 2014
PHP 5.6.0RC4 released Aug 14th 2014
PHP 5.6.0 GA released Aug 28th 2014

Fedora build

php-5.6.0-0.1.RC1.fc21 built Jun 19th 2014
php-5.6.0-0.3.RC2.fc21 built Jul 7th 2014
php-5.6.0-0.5.RC3.fc21 built Jul 31th 2014
php-5.6.0-0.6.RC4.fc21 built Aug 14th 2014
php-5.6.0-1.fc21 built Aug 24th 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)'

Contingency Plan

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

Contingency mechanism: Wait for 5.6.0RC1 for rawhide import, so we'll, at least, ship a RC. In case of big trouble, revert to F20 version (5.5.x).

Contingency deadline: June
Blocks release?: No
Blocks product?: No

Documentation

Upstream documentation: Migrating from PHP 5.5.x to PHP 5.6.x (work in progress, should be ready for final)

Release Notes

@@ Line 1: / Line 1: @@
-{{admon/important | 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.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
 <!-- Self Contained or System Wide Change Proposal?
 Use this guide to determine to which category your proposed change belongs to.
@@ Line 28: / Line 26: @@
 == Owner ==
-<!--
-For change proposals to quality as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
-This should link to your home wiki page so we know who you are.
--->
 * Name: [[User:remi|Remi Collet]]
-<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
+* Email: remi @ fedora project DOT org
-* Email: <your email address so we can contact you, invite you to meetings, etc.>
+* Release notes owner: [[User:Pbokoc| Petr Bokoc]] pbokoc at redhat dot com
-* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
 <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
 * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
@@ Line 46: / Line 39: @@
 == Current status ==
 * Targeted release: [[Releases/21 | Fedora 21 ]]
-* Last updated: (DATE)
+* Last updated: 2014-06-19
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
 Bugzilla states meaning as usual:
@@ Line 55: / Line 48: @@
 CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 -->
-* Tracker bug: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1089323 #1089323]
+Upstream releases:
+* PHP 5.6.0alpha3 released Mar 6th 2014
+* PHP 5.6.0beta1 released Apr 11th 2014
+* PHP 5.6.0beta2 released May 2nd 2014
+* PHP 5.6.0beta3 released May 15th 2014
+* PHP 5.6.0beta6 released Jun 6th 2014 (last before RC)
+* PHP 5.6.0RC1 released Jun 19th 2014
+* PHP 5.6.0RC2 released Jul 3rd 2014
+* PHP 5.6.0RC3 released Jul 31th 2014
+* PHP 5.6.0RC4 released Aug 14th 2014
+* PHP 5.6.0 GA released Aug 28th 2014
+Fedora build
+* php-5.6.0-0.1.RC1.fc21 built Jun 19th 2014
+* php-5.6.0-0.3.RC2.fc21 built Jul 7th 2014
+* php-5.6.0-0.5.RC3.fc21 built Jul 31th 2014
+* php-5.6.0-0.6.RC4.fc21 built Aug 14th 2014
+* php-5.6.0-1.fc21 built Aug 24th 2014
 == Detailed Description ==
-<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 Important changes in this new version:
@@ Line 74: / Line 85: @@
 New tool:
-* [https://wiki.php.net/rfc/phpdbg PHP debugger]
+* [https://wiki.php.net/rfc/phpdbg PHP debugger] provided in the new '''php-dbg''' subpackage (phpdbg command)
 == Benefit to Fedora ==
-Provides the latest PHP version.
+Provides the latest upstream PHP version.
 == Scope ==
@@ Line 84: / Line 95: @@
 * 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:  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+(pure) PHP extension owners: ensure compatibility, usually this is detected by running upstream test suite, when exists.
-* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+PHP webapp owners: test
-<!-- 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 -->
+* 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.  -->
+N/A.
-* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Policies and guidelines:  <!-- 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. -->
+N/A.
 == Upgrade/compatibility impact ==
@@ Line 99: / Line 113: @@
 == 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:
-. What special hardware / data / etc. is needed (if any)?
-. How do I prepare my system to test this change? What packages
-need to be installed, config files edited, etc.?
-. What specific actions do I perform to check that the change is
-working like it's supposed to?
-. What are the expected results of those actions?
--->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+Fedora 19/20 users can use backported packages from [http://blog.famillecollet.com/post/2014/03/02/New-repository-remi-php56 remi-php56] repository.
-N/A (not a System Wide Change)
 == User Experience ==
-<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
+Web developer will get the latest upstream PHP version.
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == Dependencies ==
-<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
+Mass rebuild need: from repoquery --whatrequires 'php(zend-abi)'
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+== Contingency Plan ==
-N/A (not a System Wide Change)
+According to upstream roadmap, 5.6.0 final should be released around June.
-== Contingency Plan ==
 <!-- 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 for rawhide import, so we'll, at least, ship a RC. In case of big trouble, revert to F20 version (5.5.x).
 <!-- 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? -->
-* 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 ==
-<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+Upstream documentation: [http://www.php.net/manual/en/migration56.php Migrating from PHP 5.5.x to PHP 5.6.x] (work in progress, should be ready for final)
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == Release Notes ==
@@ Line 149: / Line 145: @@
 -->
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF21]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 156: / Line 152: @@
 <!-- Select proper category, default is Self Contained Change -->
-[[Category:SelfContainedChange]]
+<!-- [[Category:SelfContainedChange]] -->
-<!-- [[Category:SystemWideChange]] -->
+[[Category:SystemWideChange]]

Search

Changes/Php56: Difference between revisions