Hello everyone,
As you may know, Zend recently open sourced ZendOptimizer+ with a PHP
Licence.
We are planning to merge it to PHP5.5 Core (discussions on Mailing lists
and IRC) and have it bundled with PHP5.5 final release stable.
For this, we need to merge new code to 5.5 as well as have a testing period
for this new feature.
As RMs, David and I decided then to change the original release plans for
5.5.
5.5 will benefit a new alpha (5th), on thu 21st Feb. ZO+ will be merged for
this alpha.
Then, we are planning to release the first beta on March the 7th. We remind
you that beta stage means feature freeze. We won't accept new features code
after the first beta is released.
This is a (about) one month delay compared to original planning (first beta
was planned for Feb 7th), but it is needed.
You will find more information about ZO+ integration on the wiki, at
https://wiki.php.net/rfc/optimizerplus
Julien Pauli and David Soria Parra
2013/2/15 Julien Pauli jpauli@php.net:
Hello everyone,
As you may know, Zend recently open sourced ZendOptimizer+ with a PHP
Licence.
We are planning to merge it to PHP5.5 Core (discussions on Mailing lists
and IRC) and have it bundled with PHP5.5 final release stable.
Correct me if I am wrong, but this is part of the following RFC:
https://wiki.php.net/rfc/optimizerplus which contains some voting
options.
Isn't a vote supposed to happen before it is actually merged or did
I miss something (#pecl ?).
Patrick
On Fri, Feb 15, 2013 at 7:19 AM, Patrick ALLAERT patrickallaert@php.netwrote:
2013/2/15 Julien Pauli jpauli@php.net:
Hello everyone,
As you may know, Zend recently open sourced ZendOptimizer+ with a PHP
Licence.
We are planning to merge it to PHP5.5 Core (discussions on Mailing lists
and IRC) and have it bundled with PHP5.5 final release stable.Correct me if I am wrong, but this is part of the following RFC:
https://wiki.php.net/rfc/optimizerplus which contains some voting
options.
Isn't a vote supposed to happen before it is actually merged or did
I miss something (#pecl ?).
I must have missed the discussion where the voting was skipped, but I am
kind of concerned that such a big change is going to make it into a feature
frozen version (where we won't be able to say this should be removed (BC
and all that)) without a vote.
I'm not necessarily saying I'm opposed to this addition as I think it's
great, but I'd like an opportunity to test it out first and play around
with it for a few weeks. It's hard to find major problems without a lot of
testing and then our biggest problem is always BC. We always find BC to be
one of the biggest reasons to hold off on changing stuff.
I have looked at the code but in my experience you don't find real bugs
until you start testing code you already have working in production on
these patches to find the really annoying bugs.
Patrick
Hi Julien,
Am 15.02.2013 um 13:05 schrieb Julien Pauli jpauli@php.net:
Hello everyone,
As you may know, Zend recently open sourced ZendOptimizer+ with a PHP
Licence.
We are planning to merge it to PHP5.5 Core (discussions on Mailing lists
and IRC) and have it bundled with PHP5.5 final release stable.
I'm sorry, but you must be kidding doing such a change and skipping the RFC process altogether. This will seriously hurt the acceptance of the whole RFC process and there won’t be a good argument against people just committing random changes without an RFC. How should I convince somebody with a working pull request to go ahead and deal with an RFC when we introduce changes like that "just like that".
Can we please stop the process insanity and stick to our own rules (or change them in a transparent way).
Thanks,
Lars