Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65675
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5110FE4B.8020406@lsces.co.uk>
References: <CAOfzkkz3DC+aVb4c73QHGRzZv=1z=nG4uexdJh2n8h3ATGBBOA@mail.gmail.com>
	<CAEZPtU6UdX4uyR7tLomi==DNbmJduHoxa=qmb+dd2bJQKcoxjw@mail.gmail.com>
	<CAOfzkkwQNKRrX+MQ3JutkVWmHsCLZetJMp7AubA52E+=MSCcXw@mail.gmail.com>
	<510EBF98.4060900@lerdorf.com>
	<CAOfzkkwU4=K86582q1kgh_w2Ecubxij-ExecBLF_aHEWMY=dew@mail.gmail.com>
	<CAKOpQSyuKoSY8JGNhYUxPNTECR30Kk8j8MY5r4tY0qS_xBju2A@mail.gmail.com>
	<CAOfzkkwLODYXEyzEb1uNp6+ANUSZ9w80p3L7S5YoT6iGA1zRhA@mail.gmail.com>
	<5110AFFB.8040303@lerdorf.com>
	<5110BF7F.90508@lsces.co.uk>
	<1360065708.95691.YahooMailNeo@web133004.mail.ir2.yahoo.com>
	<5110FE4B.8020406@lsces.co.uk>
Date: Tue, 5 Feb 2013 16:54:26 +0100
Message-ID: <CAEZPtU6yNikOhrO3s_R8dx-WMVJ-nxLcKvB9AmMFyB=6+BdS5Q@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Proposal for serious BC compatibility aka language versioning
From: pierre.php@gmail.com (Pierre Joye)

On Tue, Feb 5, 2013 at 1:42 PM, Lester Caine <lester@lsces.co.uk> wrote:
> hakre wrote:
>>>
>>> In reality we have to make choices where we DO spend time. There is still
>>> a mile
>>> >of code out there being used live which is running perfectly on the
>>> > PHP5.2
>>> >infrastructure. That needs testing and reworking on PHP5.3 and then
>>> > PHP5.4
>>> >before we get around to 5.5.
>>
>> Why do you change the infrastructure if the code does not need it? I mean,
>> provide the infrastructure the code needs and done. There is more than one
>> vendor that offers support for PHP 5.2 infrastructure in the market. What's
>> the deal?
>
>
> The point here is supporting customers that I've 'acquired' who are
> currently hosted on services that control that infrastructure. The long term
> aim is to move them to servers under our control, but in the meantime until
> contracts run out we have to live with such activity as 'We will be updating
> to PHP5.3 on the 1st April'. The problem now is how to deal with that
> situation, and paying up outstanding contracts may be the solution. The code
> needs updating, and updating to 5.4 would be useful, but short term
> everything needs testing and fixing for PHP5.3 :(
>
> The whole reason that ISP's are currently moving from PHP5.2 to PHP5.3
> rather than PHP5.4 is that there is a better chance that their client sites
> will continue to work.
> http://w3techs.com/technologies/history_details/pl-php/5 use of PHP5.1 is
> slowing faster than 5.4 use is growing.


If you do commercial support for customers and do not control the
environment and/or use shared hosting, then something is totally wrong
in your business model. It is also really off topic, in this mailing
list or in this discussion.

Cheers,
--
Pierre

@pierrejoye