Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17288 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95181 invoked by uid 1010); 17 Jul 2005 20:07:04 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 95166 invoked from network); 17 Jul 2005 20:07:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jul 2005 20:07:04 -0000 X-Host-Fingerprint: 129.21.60.6 blacksheep.csh.rit.edu Tru64 v5.1a JP4 (or OpenVMS 7.x on Compaq 5.x Received: from ([129.21.60.6:3803] helo=blacksheep.csh.rit.edu) by pb1.pair.com (ecelerity HEAD r(6212)) with SMTP id 87/FB-10960-76ABAD24 for ; Sun, 17 Jul 2005 16:07:03 -0400 Received: from fury.csh.rit.edu (fury.csh.rit.edu [IPv6:2001:470:1f00:135:a00:20ff:fe8d:5399]) by blacksheep.csh.rit.edu (Postfix) with ESMTP id 0FCEB265B for ; Sun, 17 Jul 2005 16:07:01 -0400 (EDT) Received: by fury.csh.rit.edu (Postfix, from userid 37404) id BA6CE1528; Sun, 17 Jul 2005 16:07:00 -0400 (EDT) Date: Sun, 17 Jul 2005 16:07:00 -0400 To: internals@lists.php.net Message-ID: <20050717200659.GA3956@csh.rit.edu> Mail-Followup-To: internals@lists.php.net References: <20050712105234.5dhkvvd6ghcsw8sg@marina.horde.org> <20050712212026.5bd2dbbb.pierre@dotgeek.org> <42D42430.5060001@prohost.org> <20050712161703.rf2hn68dptcswssw@marina.horde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [PHP-DEV] php 4.4 BC break From: jon@php.net (Jon Parise) On Tue, Jul 12, 2005 at 10:33:14PM +0100, Nicholas Telford wrote: > Firstly, a major version number increment implies a major change (4.2.0 > and 4.3.0 had much more major changes than this iirc). Secondly, as far > as I'm aware, it doesn't issue a warning, it issues notices which, and > this has been stressed on many occasions, should not be displayed on > production servers. Sure, but the issue here has very little to do with production servers. What's happening is that site administrators are upgrading their test environments and then checking their existing software to make sure it hasn't broken. They see all of these new warnings and then report them back to the application developers. It would be much easier for each application developer to redirect that site administrators to a note on php.net explaining the change than for the application developers to explain the change over and over again. Or, even better, the administrator would find it there themself. -- Jon Parise (jon of php.net) :: The PHP Project (http://www.php.net/)