php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Request #10084 Release Quality
Submitted: 2001-03-31 00:02 UTC Modified: 2001-03-31 16:48 UTC
From: augustz at bigfoot dot com Assigned:
Status: Not a bug Package: Feature/Change Request
PHP Version: 4.0 Latest CVS (30/03/2001) OS: NA
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: augustz at bigfoot dot com
New email:
PHP Version: OS:

 

 [2001-03-31 00:02 UTC] augustz at bigfoot dot com 
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...

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-03-31 03:17 UTC] rasmus@php.net 
And I assume you will be pitching in and helping out on each front?  We don't set out to have a buggy release.  There is a QA team and a QA process for this purpose.  Feel free to join it.  See http://qa.php.net

Compiling for command-line is trivial.  Just don't add --with-apxs ot --with-apache and you have the standalone parser.

And your bluesky stuff about adding bloat numbers to the manual.  Go for it.  That just takes someone sitting down and writing down the numbers.  You are more than qualified and more than welcome to do this.  Note however that this will be different on most platforms, so be sure to do each one.  Might even have significant differences across versions of the same operating system, linkers, compilers, libc's, different versions of the 3rd party libs, etc.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Thu Apr 24 14:01:29 2025 UTC