-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 05.02.2013 09:14, schrieb Lester Caine: > f 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. > > This is perhaps the main problem with accelerating the release > timetable in that there simply is not enough time to bring > everybody along? So something has to give and at the moment for me > it's going to have to be 5.5 ... but by the time all the legacy > stuff is up to 5.4 you will be way off in the distance :(
Actually, it doesn't matter. Three years worth of changes are just the same, be it in one or three versions. With faster and less radical steps, there is a better chance the provider's upgrade cycle fits PHP's upgrade cycle and just misses by one or two minor changesets rather than one big. It also makes "make the site work again" a more regular, but easier task and increases customers' awareness that unmaintained web software will not continue to run indefinately. Just as putting your legacy DOS app onto a new computer after the 15 year old legacy system finally broke down will require some brains to "make work again". As a supporter / hired external consultant I would like that. - -- Ralf Lang Linux Consultant / Developer -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEQ6/UACgkQCs1dsHJ/X7Dp+QCg0prN0juyUojOuJRJ5GM1TwdS sr8An28l0a18Idsfh6kw/8xPZ8cQwrJH =65H6 -----END PGP SIGNATURE----- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
