Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55588 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66160 invoked from network); 22 Sep 2011 17:44:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Sep 2011 17:44:06 -0000 Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 config.schlueters.de Received: from [217.114.211.66] ([217.114.211.66:37847] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 88/23-45260-4E37B7E4 for ; Thu, 22 Sep 2011 13:44:05 -0400 Received: from [192.168.2.230] (ppp-93-104-58-124.dynamic.mnet-online.de [93.104.58.124]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 9274577A21; Thu, 22 Sep 2011 19:44:01 +0200 (CEST) To: Clint Byrum Cc: internals In-Reply-To: <1316709104-sup-2744@fewbar.com> References: <4E790B82.6090805@akbkhome.com> <8C.A0.17510.E4DE97E4@pb1.pair.com> <1316615094.2810.5.camel@guybrush> <1316629502-sup-831@fewbar.com> <20110922134956.GA28577@panix.com> <1316709104-sup-2744@fewbar.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 22 Sep 2011 19:43:02 +0200 Message-ID: <1316713382.1290.60.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.2 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: is_a() - again - a better fix From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Thu, 2011-09-22 at 10:27 -0700, Clint Byrum wrote: > So I'm not sure what you would expect from distros, but please share > and we'll setup automated tests, call for our users to test, whatever > it takes to avoid this type of situation. This issue is not about packagers specifically. What we need is that more application and library developers test it. I think it is a shame that PEAR, a php.net project like PHP itself, breaks. This must not happen. I have no idea what to do though. We have a list of "primary testers" where I usually get one or two responses but most goes into the void. When talking to application maintainers they don't have the time or similar reasons and hope/trust that others will test enough. Maybe a good thing in all this is that it is wakening ... What else can we do? - More application tests? That's a nice idea but not knowing the applications it is relatively time consuming to analyze test failures in there (not to mention that many projects have a bad test coverage ..) that happen easily due to "unimportant" changes. johannes