PHP 4.0 Bug #10084: Release Quality
| From: | augustz at bigfoot dot com | Date: | Sat, 31 Mar 2001 05:02:29 +0000 |
| Subject: | PHP 4.0 Bug #10084: Release Quality | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-50398@lists.php.net to get a copy of this message | ||
From: augustz@bigfoot.com
Operating system: NA
PHP version: 4.0 Latest CVS (30/03/2001)
PHP Bug Type: Feature/Change Request
Bug description: Release Quality
As a happy user of PHP I'd love it if
a) Releases (4.0.5) could be installed across server farms, compiled to commandline versions to
support shell/console scripting, packaged in various ways for different workloads (ie adding IMAP)
without the sinking fear that in a few days to a week or two I'll see pl1, pl2, pl3 and have to
go through the who rigamarole again. So fewer patches, more RC's :)
b) Extensions that are broken do not ship with the distribution. The quality of the extensions
reflects on php itself. A few always seem to be borked but live on through releases. The folks that
want to fix borked extensions can probably do so even if they are not included in the distro. Hand
in hand with that is at least keeping a rough idea (or requiring the submitter to) on keeping up to
date with extensions, which often are based on evolving external libraries and projects.
c) Bluesky: Bloat numbers on the manual for the different extensions. This contibutes x bytes to
cgi/apache module or whatever...
--
Edit Bug report at: http://bugs.php.net/?id=10084&edit=1