Am 15.12.2014 20:43 schrieb "Zeev Suraski" <z...@zend.com>: > > The extra pain associated with migrating to an interim > version - that does nothing but spew warnings in the right places -and > obviously doesn't have any of the other features of 7 - doesn't seem to be a > worthwhile experience for most users.
I dont't know about "most users", I can only speak for myself from our small shop (in the big scheme of things...) production and development experience. I compile PHP myself for our setup, and have a nice compilation and deployment environment where I can easily throw new versions separately onto developer hosts and production hosts. We made our codebase E_STRICT|E_DEPRECATED-clean on the transition from 5.3 to 5.4, meanwhile migrated to 5.5, and soon to 5.6, with almost no pain, by first running new versions on developer machines and then on one of several production servers, where possibly issues are visible pretty fast. Now with PHP 7 promising potential for incompatibilities in a lot more areas, it would be, to us, a really useful option to have a 5.7 that is operationally fully compatible with 5.6 with added E_DEPRECATED for things bound to break. With that we could A) rub the developers' noses in the relevant deprecation messages for a while, _and_ run one or more rounds of one-of-the-production -server tests, gathering more deprecation messages there without fear of user visible effects. I cannot judge how much effort such a 5.7 would be for you as developers, and for the release managers, but I definitely would appreciate the effort, and I'm 100% sure that it would speed up our eventual adoption of PHP 7 by at least half a year, because the process would be much less risky. best regards Patrick
