Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75840 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77104 invoked from network); 22 Jul 2014 12:39:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jul 2014 12:39:45 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; 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:49396] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 56/50-09870-09B5EC35 for ; Tue, 22 Jul 2014 08:39:44 -0400 Received: (qmail 4482 invoked by uid 89); 22 Jul 2014 12:39:41 -0000 Received: by simscan 1.3.1 ppid: 4476, pid: 4479, t: 0.0735s scanners: attach: 1.3.1 clamav: 0.96/m:52 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 22 Jul 2014 12:39:41 -0000 Message-ID: <53CE5B8D.8050304@lsces.co.uk> Date: Tue, 22 Jul 2014 13:39:41 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.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] RFC: Move phpng to master From: lester@lsces.co.uk (Lester Caine) On 22/07/14 13:17, Ferenc Kovacs wrote: > The discussion seems to be sidetracked by the topic on when should we > release PHP-NEXT and what else should it contains. > Could we agree to put that aside for now, and agree to discuss this later, > after we managed to have a consensus on merging phpng to master? > I think that it is an important question, but not having phpng in master > block the other features/changes as well, and we don't have to decide about > the roadmap/features for PHP-NEXT right now. PHPNext is a side issue as it does not need phpng ... What seems to be missing here is any real possibility of a review of all the aspects of phpng and IF each of those make sense - in light of developments others have been working on. It does sound very much as if phpng is already a done deal and it just need to be rubber stamped into the main development stream? There has been complaints about not being able to review decisions made behind closed doors but my own concern as always is the effect on extensions I use. These sorts of substantial reworks broke interbase for many versions back in the 5.0/5.1 days and it was not until 5.1.6 that a working version was restored! Interbase is not even included in phpng yet ... as are other database interfaces ... areas where performance can be tuned by offloading work rather than downloading data unnecessarily. -- 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