cvs: pearweb /weeklynews 20030119.en.html
| From: | Stig Bakken | Date: | Sun, 19 Jan 2003 07:04:47 +0000 |
| Subject: | cvs: pearweb /weeklynews 20030119.en.html | ||
| Groups: | php.pear.cvs | ||
| Request: | Send a blank email to pear-cvs+get-8399@lists.php.net to get a copy of this message | ||
ssb Sun Jan 19 02:04:47 2003 EDT
Modified files:
/pearweb/weeklynews 20030119.en.html
Log:
* clarify some PECL stuff :)
Index: pearweb/weeklynews/20030119.en.html
diff -u pearweb/weeklynews/20030119.en.html:1.5 pearweb/weeklynews/20030119.en.html:1.6
--- pearweb/weeklynews/20030119.en.html:1.5 Sat Jan 18 20:35:38 2003
+++ pearweb/weeklynews/20030119.en.html Sun Jan 19 02:04:46 2003
@@ -64,11 +64,15 @@
<br \><br \>
The reason we do this is to make PHP's release process manageable.
Today a PHP release takes several months. By importing stable releases
-of extensions in PECL, we will have fewer unknowns that need to be
+of extensions in PECL into the PHP source distribution, rather than having
+them as part of PHP CVS, we will have fewer unknowns that need to be
tested during PHP's QA process, because the extensions from PECL have
already been through their own QA. Hopefully this will reduce the PHP
release process to weeks rather than months, and increase the general
-quality of all extensions bundled with PHP.
+quality of all extensions bundled with PHP. I want to emphasise that
+this pickling process does <i>not</i> mean that users will have no
+extensions bundled with PHP. PHP will still bundle exceptions, but
+higher quality is expected of bundled extensions in PHP 5.
<br \><br \>
Also, if extensions are built shared (not compiled directly into PHP,
but as dynamically loadable libraries), it will be possible to upgrade