Ilia,
On Thu, Feb 28, 2013 at 8:54 AM, Ilia Alshanetsky <i...@prohost.org> wrote: > Zeev has an excellent point here, my own research shows that 5.4, a > year after release had somewhere in the 2% adoption rate. The major > reason being is the lack of a stable, production ready op-code cache. > To release 5.5 without a good solution for that problem, would not > make the situation better, if anything it would make it very > intimidating to users to jump 2-3 versions directly to 5.6. Thus > leaving us with a massive user base running legacy, unsupported > versions containing unresolved bugs and vulnerabilities. Something, > which I don't think would be a very good thing for the future of PHP. > To be fair, the 5.5 situation without pulling in ZO+ is NOT the same as 5.4 was. Today, right now, there exists at least one stable open source opcode cache. 5.4 had none for many months after release. So I'm not sure if the same pressures exist. The discussion now is if we delay 5.5 to spend the time pulling it in core. But either way (in core or not), ZO+ is open and working on 5.5 alpha. So we could skip the core import, and just ship it today as gold, and it would be adoptable straight away (unlike how 5.4 was). > Ultimately, I think it is better to wait a month or two (if that is > what it takes) and have a solid release people can safely upgrade > their production environments to, rather than strictly adhere to a set > release cycle and delivery a partial solution. That's the thing though, it wouldn't be a partial solution. It would be exactly where 5.2, 5.3 and 5.4 are today, with the addition of several highly wanted features. I'd rather delay 5.6, and do a deeper integration into the engine. Then at least there's something to gain by pulling it into core, rather than just having it be a compile-time-flag as opposed to a pecl installation (which doesn't buy us *that* much)... My standpoint at least... Anthony
