Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66308
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <512E7870.7010208@lerdorf.com>
References: <435a322ccb14090d3bcf6bf8a110396d@mail.gmail.com>
	<CAH-PCH5wD99wYKxBo0mKK2QQkJe_toQP+4pB1KXCVfqCYVAoJA@mail.gmail.com>
	<512E7870.7010208@lerdorf.com>
Date: Wed, 27 Feb 2013 23:16:31 +0100
Message-ID: <CAEZPtU6E1AHJSv5zhriu8GbAt1-XvjyA_2_NKDpVcPr-hpsp0w@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Ferenc Kovacs <tyra3l@gmail.com>, Zeev Suraski <zeev@zend.com>, 
	PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP distribution
From: pierre.php@gmail.com (Pierre Joye)

On Wed, Feb 27, 2013 at 10:19 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> On 02/27/2013 01:01 PM, Ferenc Kovacs wrote:

> This is where I think we have a big disconnect. This yearly release plan
> is meaningless for most people because there is no way the current
> opcode cache situation can keep up with that. PHP 5.4 wasn't really
> released until APC was mostly stable with it which was 6+ months after
> the release.

That's why having a builtin opcode cache should be a long term goal.
And that's why it will be done this way. All other ways failed.



> In order to actually get the project onto a feasible yearly release
> cycle we need to pool the few resources we do have around a single
> opcode cache implementation and push it as the one and only option as it
> will force each new shiny feature to tackle opcode support from day one

Exactly.

Now, about the yearly release, every single person I talked to love it
and want us to keep with this cycle, as well as the more frequent bugs
fixes releases. One thing we have to slightly change is to push too
many new features in each of them, but we will get there.

cheers,
-- 
Pierre

@pierrejoye