Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47435 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 28123 invoked from network); 19 Mar 2010 18:50:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Mar 2010 18:50:09 -0000 Authentication-Results: pb1.pair.com header.from=larry@garfieldtech.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=larry@garfieldtech.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 69.5.8.4 cause and error) X-PHP-List-Original-Sender: larry@garfieldtech.com X-Host-Fingerprint: 69.5.8.4 hc02.futurequest.net Linux 2.4 w/o timestamps Received: from [69.5.8.4] ([69.5.8.4:57192] helo=hc02.futurequest.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EA/78-14064-F57C3AB4 for ; Fri, 19 Mar 2010 13:50:08 -0500 Received: (qmail 6695 invoked from network); 19 Mar 2010 18:50:05 -0000 X-Originating-IP: [66.166.38.114] Message-ID: <4BA3C75C.3070403@garfieldtech.com> Date: Fri, 19 Mar 2010 13:50:04 -0500 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3 MIME-Version: 1.0 To: internals@lists.php.net References: <7B11643C-4A65-4C5F-8E45-5BAC1BC546C1@gmail.com> In-Reply-To: <7B11643C-4A65-4C5F-8E45-5BAC1BC546C1@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: PHP 5.4 branch and trunk From: larry@garfieldtech.com ("larry@garfieldtech.com") On 3/19/10 1:31 PM, Nate Abele wrote: >> The point is that, for instance, PHP 5.3 was not a trivial upgrade for coders or hosters. Sure it's mostly compatible, and you certainly can write code that works from 5.0->5.3 just fine, and if not then you're probably doing something wrong... but that's most of the PHP code out there right now. :-) And naturally you can't test your code against 5.3 until it's out. > > Larry, to mitigate this issue, please refer to the exhaustive list of instructions here: > > http://twitter.com/nateabele/status/10733251789 > > PLEASE NOTE: This also applies to user-land applications with test suites (and here I'm risking showing my ignorance by blindly assuming Drupal does, in fact, have a test suite). > > Please see http://snaps.php.net/ and http://qa.php.net/ for more information. > > Thanks, > - Nate Drupal 7 has an extensive test suite, using our own testing framework rather than phpt. (Let's not get into a debate about why that's the case; it's neither here nor there nor would I even be on just one side of it. ) But that's for a high-end project. It doesn't really help the code slingers that happen to have code they threw together that is holding back a hosting company who don't even know what "make" is. I am not saying people shouldn't be testing code. I'm saying the barrier to entry to testing common code found in the wild on a new release of PHP is higher than you seem to be assuming. --Larry Garfield