Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65875
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CACwt+JepzrYNPFPCWbbb7vNmSzz-KtKO2jV27oZyN99xWFpmFg@mail.gmail.com>
References: <CAMUwpuSVpu=93pkD8ywSNqcj=474EnkKxOhyoEScvg_axA8YPA@mail.gmail.com>
	<CACwt+JepzrYNPFPCWbbb7vNmSzz-KtKO2jV27oZyN99xWFpmFg@mail.gmail.com>
Date: Fri, 15 Feb 2013 10:34:56 -0500
Message-ID: <CAL+t6cEEVSDnzaw1kXHyh8kqYn8-VmjTtbue95L9KLRSiW2s-A@mail.gmail.com>
To: Patrick ALLAERT <patrickallaert@php.net>
Cc: Julien Pauli <jpauli@php.net>, PHP Internals <internals@lists.php.net>, 
	David Soria Parra <dsp@php.net>
Content-Type: multipart/alternative; boundary=14dae9cc95341366ff04d5c51e60
Subject: Re: [PHP-DEV] PHP 5.5 upcoming roadmap
From: theanomaly.is@gmail.com (Sherif Ramadan)

--14dae9cc95341366ff04d5c51e60
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Feb 15, 2013 at 7:19 AM, Patrick ALLAERT <patrickallaert@php.net>wrote:

> 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
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--14dae9cc95341366ff04d5c51e60--