Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55614 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54419 invoked from network); 23 Sep 2011 16:42:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Sep 2011 16:42:31 -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:47420] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BE/8A-29222-4F6BC7E4 for ; Fri, 23 Sep 2011 12:42:29 -0400 Received: from [192.168.2.230] (ppp-93-104-56-226.dynamic.mnet-online.de [93.104.56.226]) (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 ED60677C5B; Fri, 23 Sep 2011 18:42:07 +0200 (CEST) To: Matthew Weier O'Phinney Cc: internals@lists.php.net In-Reply-To: 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> <1316713382.1290.60.camel@guybrush> <4E7BBA23.2080001@lerdorf.com> <4E7BC6BF.6080702@akbkhome.com> <4E7C5A24.8080305@lerdorf.com> <4E7C5CE9.40000@lerdorf.com> Content-Type: text/plain; charset="UTF-8" Date: Fri, 23 Sep 2011 18:41:58 +0200 Message-ID: <1316796118.2289.5.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 Fri, 2011-09-23 at 12:15 -0400, Matthew Weier O'Phinney wrote: > On 2011-09-23, Rasmus Lerdorf wrote: > > On 09/23/2011 12:13 PM, Patrick ALLAERT wrote: > > > 2011/9/23 Rasmus Lerdorf > > > > 2. Maybe we should think bigger and put more focus on having large PHP > > > > frameworks and apps test every RC. Currently we notify them of RCs > > > > and just hope someone will test and report back, but that obviously > > > > isn't working. We need a Daniel Brown-like approach to this. Someone > > > > who is really annoyingly persistent and will hunt down people to > > > > test RCs and keep a sign-off checklist of projects that have given > > > > a thumbs-up on an RC. > > > > > > Solution 2: +1 > > > > > > Having a Jenkins instance which would run major framework testsuites > > > against the different versions of PHP? > > > > That would be cool, but a lot of work to maintain since every > > framework/app has different ways of testing and we'll want to test > > different versions. It seems like the best bet is to get the people who > > know the code best to maintain the tests. If we could get all of them to > > set up *and maintain* their stuff on the Jenkins instance it would be > > ideal, but that's probably dreaming in technicolor. > > I've made the decision that my team will test against RCs as soon as > they are out (and we're going to be trying to do each beta as well). If > we run into issues, we'll of course report back here. Good are also "success" reports so we know tests were run and succeeded. > That said, I think it would be good to have a notification system > whereby framework leads are all pinged on new betas and RCs, and a wiki > page where they can indicate that they've run tests (and whether or not > they had issues). That way, you could have a targetted nag list -- "Hey, > I don't see an update from you -- RUN THE TESTS!", and a deadline > whereby if they haven't run them, they accept the consequences. :) We send out mails like this: http://news.php.net/php.qa/65903 to maintainers of different PHP projects who have opted in for every RC. I usually get one response and lots of black-hole void reactions. For 5.3.9 I'll make more responses a release requirement. (have to check the current recipient list and probably update that to define that closer, will also work w/ Stas/dsp on that to have it identical for 5.4) > I could also see this being an interesting peer-pressure move -- "First > to test!", "We tested last week; how come _you_ haven't?", etc. This also means that this list has more traffic. Which makes it more likely to be ignored ... johannes