From Fedora Project Wiki
No edit summary
Line 40: Line 40:


* Update to PHP 5.4.0
* Update to PHP 5.4.0
* Build ZTS extension
* Build ZTS extensions/modules
* Provide ZTS devel stuff (in php-devel)
* Provide ZTS devel stuff (in php-devel)
* Update other extensions (mostly pecl) for latest ABI
* Update other extensions (mostly pecl) for latest ABI
Line 51: Line 51:
== Scope ==
== Scope ==
<!-- What work do the 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?-->
<!-- What work do the 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?-->
* Mass rebuild of all packages which requires php ABI, some will requires update or patch
* Test of web applications


== How To Test ==
== How To Test ==
Line 66: Line 69:
3. What are the expected results of those actions?
3. What are the expected results of those actions?
-->
-->
* test PHP web applications available in the repository
* test PHP with apache in worker mode (ZTS modules)


== User Experience ==
== User Experience ==
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
* Web developper will get the latest upstream PHP version


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature 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 feature)? -->
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature 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 feature)? -->
From repoquery --whatrequires 'php(zend-abi)'
* cups-php
* graphviz-php
* ice-php
* php-digidoc
* php-eaccelerator
* php-facedetect
* php-idn
* php-libpuzzle
* php-libvirt
* php-magickwand
* php-mapi
* php-pecl-apc
* php-pecl-gearman
* php-pecl-geoip
* php-pecl-gmagick
* php-pecl-igbinary
* php-pecl-imagick
* php-pecl-lzf
* php-pecl-mailparse
* php-pecl-memcache
* php-pecl-memcached
* php-pecl-mongo
* php-pecl-ncurses
* php-pecl-oauth
* php-pecl-radius
* php-pecl-rrd
* php-pecl-selinux
* php-pecl-solr
* php-pecl-sphinx
* php-pecl-ssh2
* php-pecl-xdebug
* php-pecl-yaml
* php-shout
* rrdtool-php
* syck-php
* uuid-php
* zorba-php


== Contingency Plan ==
== Contingency Plan ==
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  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 "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
*
* upstream [http://svn.php.net/viewvc/php/php-src/branches/PHP_5_4/NEWS?view=co NEWS]
* upstream [http://svn.php.net/viewvc/php/php-src/branches/PHP_5_4/UPGRADING?view=co UPGRADING] (for web applications developer)
* upstream [http://svn.php.net/viewvc/php/php-src/branches/PHP_5_4/UPGRADING.INTERNALS?view=co UPGRADING.INTERNALS] (for extension developer)


== Release Notes ==
== Release Notes ==

Revision as of 12:10, 27 December 2011

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 FEATURE.
Set a Page Watch
Make sure you click watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed



PHP 5.4

Summary

To provide the latest PHP stack.

Owner

  • Email: Fedora AT SPAMFREE FamilleCollet DOT com

Current status

  • Targeted release: Fedora 17
  • Last updated: 2011-12-27
  • Percentage of completion: 0%


Detailed Description

Fedora provides PHP 5.3.x since version 12. Zts module for apache is provided without any extension/module, this lack make it nearly unusable.

PHP 5.4.0RC4 was published for christmas, see annouce. Finale version should be available before fedora 17.

  • Update to PHP 5.4.0
  • Build ZTS extensions/modules
  • Provide ZTS devel stuff (in php-devel)
  • Update other extensions (mostly pecl) for latest ABI
  • Update PHP Guidelines

Benefit to Fedora

Provides the latest PHP major version.

Scope

  • Mass rebuild of all packages which requires php ABI, some will requires update or patch
  • Test of web applications


How To Test

  • test PHP web applications available in the repository
  • test PHP with apache in worker mode (ZTS modules)

User Experience

  • Web developper will get the latest upstream PHP version

Dependencies

From repoquery --whatrequires 'php(zend-abi)'

  • cups-php
  • graphviz-php
  • ice-php
  • php-digidoc
  • php-eaccelerator
  • php-facedetect
  • php-idn
  • php-libpuzzle
  • php-libvirt
  • php-magickwand
  • php-mapi
  • php-pecl-apc
  • php-pecl-gearman
  • php-pecl-geoip
  • php-pecl-gmagick
  • php-pecl-igbinary
  • php-pecl-imagick
  • php-pecl-lzf
  • php-pecl-mailparse
  • php-pecl-memcache
  • php-pecl-memcached
  • php-pecl-mongo
  • php-pecl-ncurses
  • php-pecl-oauth
  • php-pecl-radius
  • php-pecl-rrd
  • php-pecl-selinux
  • php-pecl-solr
  • php-pecl-sphinx
  • php-pecl-ssh2
  • php-pecl-xdebug
  • php-pecl-yaml
  • php-shout
  • rrdtool-php
  • syck-php
  • uuid-php
  • zorba-php

Contingency Plan

Documentation

Release Notes

Comments and Discussion