Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85630 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 74550 invoked from network); 1 Apr 2015 08:24:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Apr 2015 08:24:30 -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:49140] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C6/F1-56894-C3BAB155 for ; Wed, 01 Apr 2015 03:24:29 -0500 Received: (qmail 490 invoked by uid 89); 1 Apr 2015 08:24:26 -0000 Received: by simscan 1.3.1 ppid: 481, pid: 486, t: 0.1301s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@109.156.131.40) by mail4.serversure.net with ESMTPA; 1 Apr 2015 08:24:26 -0000 Message-ID: <551BAB39.9020009@lsces.co.uk> Date: Wed, 01 Apr 2015 09:24:25 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: internals@lists.php.net References: <55193060.5000804@php.net> <55199AE8.4090100@gmail.com> <551AFC1E.6010501@gmail.com> <551B8FF1.7080002@gmail.com> In-Reply-To: <551B8FF1.7080002@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] What's our official stance on small self-contained additions in a micro version From: lester@lsces.co.uk (Lester Caine) On 01/04/15 07:28, Stanislav Malyshev wrote: > You may think if we ban > enhancement then people would jump to 7.x in droves - but I have yet to > see anybody taking decisions this way. So far statistics says people > still are in 5.3 and 5.4 massively - though we do not add features there > for quite some time. So it doesn't look like not adding features makes > people to move on. Practical example. I still have several sites on 5.2 hosting. They need upgrading before they will run on 5.4 ... and while they would work on 5.3 with warnings switched off there is no point making that switch. They HAVE to be modified for 5.4, and that takes time :( Retesting all of the 5.4 stuff on a later version will wait until everything is on 5.4! None of these 'small self-contained additions' have any use in maintaining the existing sites, and so there is little point even bothering with 5.5 or 5.6 if 7.0 is going to be out before the last of the 5.2 sites have been upgraded. Hence my development server having both 5.4 and 7.0 running in parallel. Yes 5.6-latest is a third option on that but only until 7.0 IS released. Th switch to 7.0 will not be because of the 'new additions'. Even type hinting will only be a hindrance to be lived with rather than a 'must have' feature simply because it does nothing to help the real problems of data validation! That code is already present and working. The ONLY reason for moving forward is to keep what is currently working perfectly on 5.2 still working on a later version. Renaming everything to some new standard gives nothing but restoring the performance improvements that eaccelerator currently provides is another holding up a move from 5.4 ... -- 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