Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55612 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44303 invoked from network); 23 Sep 2011 16:15:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Sep 2011 16:15:45 -0000 X-Host-Fingerprint: 96.2.18.191 host-191-18-2-96.midco.net Date: Fri, 23 Sep 2011 12:15:44 -0400 Received: from [96.2.18.191] ([96.2.18.191:12890] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B7/78-29222-0B0BC7E4 for ; Fri, 23 Sep 2011 12:15:44 -0400 Message-ID: To: internals@lists.php.net 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> User-Agent: slrn/pre1.0.0-18 (Linux) X-Posted-By: 96.2.18.191 Subject: Re: [PHP-DEV] Re: is_a() - again - a better fix From: weierophinney@php.net (Matthew Weier O'Phinney) 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. 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. :) I could also see this being an interesting peer-pressure move -- "First to test!", "We tested last week; how come _you_ haven't?", etc. -- Matthew Weier O'Phinney Project Lead | matthew@zend.com Zend Framework | http://framework.zend.com/ PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc