Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86212 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 36759 invoked from network); 14 May 2015 08:57:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 May 2015 08:57:52 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:45964] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B8/B4-31470-F8364555 for ; Thu, 14 May 2015 04:57:51 -0400 Received: (qmail 9715 invoked by uid 89); 14 May 2015 08:57:48 -0000 Received: by simscan 1.3.1 ppid: 9708, pid: 9711, t: 0.0746s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 14 May 2015 08:57:48 -0000 Message-ID: <5554638B.4090807@lsces.co.uk> Date: Thu, 14 May 2015 09:57:47 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Branching off PHP7 and electing RMs From: lester@lsces.co.uk (Lester Caine) On 14/05/15 06:19, Pierre Joye wrote: > Why you and Anatol makes perfect sense. Kalle can help a lot with the > numerous tasks that will pop up, testing patches cherry picks and all > these time consuming tasks. I'd second that, as long as all three of you are happy to provide the time? I would take it a step further though and while there should not be major compatibility problems, some of the major frameworks may be able to help out by sorting their own 'point of contact'. I still remember the bug reports generated by PHP5 which in practice were simply areas where one framework or another still had to iron out updating their end of the code. I suspect this time around once the RC's are published there will be ten times more eyes all complaining something does not work? Even a team of three WILL need some help ... so triage by the relevant experts to identify what are real bugs will be helpful? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk