Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62482
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.184 cause and error)
Message-ID: <5038D2B1.6060704@lsces.co.uk>
Date: Sat, 25 Aug 2012 14:27:13 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120604 Firefox/13.0 SeaMonkey/2.10
MIME-Version: 1.0
To: "internals@lists.php.net >> PHP internals" <internals@lists.php.net>
References: <503897B4.8020303@lsces.co.uk> <CAH-PCH7XPDTxC5J=amh5Z4hYvWjC3+_TioVA=uztzmdkhnL_gw@mail.gmail.com> <CADyq6sL-qBxowHFh3E=_n710aww2Uf2Dzdb7tWGZSjkrvQmzsQ@mail.gmail.com> <5038C04D.9080509@lsces.co.uk> <5038C0F8.9060008@ajf.me>
In-Reply-To: <5038C0F8.9060008@ajf.me>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Older style frameworks ...
From: lester@lsces.co.uk (Lester Caine)

Andrew Faulds wrote:
> OK Lester, you've whined enough, what do you want us to do? Freeze development
> for 5 years so ISPs can slowly catch up, or something?

Simply taking care to provide fixed point that we can work to would have helped. 
LTS versions have been rejected in the past, but PLEASE can we stop producing 
yet another PHP5.x version and make PHP5.4 an end point that we can work to and 
produce comprehensive upgrade notes to help people get to that point. Make that 
an LTS version and move new development over to PHP6 where there would be more 
'flexibility' to break things if needs be.

PHP5.2 is the current LTS almost by default, but one thing that we need to try 
and do is get the user community to move to PHP5.4 rather than the current move 
to PHP5.3 on many ISP's ( at least the one's I'm having to deal with ). If 
PHP5.4 is ring fenced then at least we have a point to aim for? Currently the 
situation on the ground is that PHP5.3 is the next production version for ISP's 
despite the fact that it's not supported!

I was reconsidering a point I made earlier, and all that we need is a 'legacy' 
php.ini that would provide a cleaner base for ISP's moving from PHP5.2 and also 
a reference point so we can document changes needed to the older code to bring 
it up to date ... strict compliant without any deprecated warnings. A 'matching' 
php.ini for PHP5.3 would help things in the interim. Having to manage sites on 
PHP5.2 and 5.3, while testing the same sites on 5.4 is my current situation, and 
having PHP5.5 looming in the background is just another irritation.

I have no doubt that it will take some years for PHP5.4 to replace 5.2, but at 
least we will have a fixed target to work with?

-- 
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