On Tue, Feb 5, 2013 at 1:42 PM, Lester Caine <les...@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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
