Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:66523 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20554 invoked from network); 7 Mar 2013 16:06:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Mar 2013 16:06:55 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain zend.com does not designate 209.85.219.47 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.219.47 mail-oa0-f47.google.com Received: from [209.85.219.47] ([209.85.219.47:60731] helo=mail-oa0-f47.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B8/43-31723-E1BB8315 for ; Thu, 07 Mar 2013 11:06:54 -0500 Received: by mail-oa0-f47.google.com with SMTP id o17so769260oag.6 for ; Thu, 07 Mar 2013 08:06:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:references:in-reply-to:mime-version:x-mailer :thread-index:date:message-id:subject:to:cc:content-type :x-gm-message-state; bh=+JLNY5G1rHUeIkd3r8AfOouMrz56a0a04kptSU77YXk=; b=oAngeZQZyxa61cWxUkbKl34HLKkJF0EVYQKtxkKUIcoHsw+QgiNLJyPfw1lARf0rQC epgF5QByZAYsb6A8HkSQcttr2TrseFmyPbvG3nYzRdpcWcPX+pGHU+lieNpjp7IIYn0u KxPLcvyhpS6UjiccfhARAhmFJp66Fqv6aQtOV2IbfBNHmcK4BggD9dg2mbc22RVxiA6N okejuF7v7ToWZbMmLy8kZ1NAqkswO+Br13yAJpcpWyUjkdbf5rVSTU84y1uHVvToorg7 TDhQAp5MAaZsruKy44hAjBXLWc9pUb4G2VJmdsjW9uLWrFeTmE7ta+u3GAVUEUBYoyZn zitA== X-Received: by 10.60.170.101 with SMTP id al5mr25877300oec.48.1362672411490; Thu, 07 Mar 2013 08:06:51 -0800 (PST) References: <435a322ccb14090d3bcf6bf8a110396d@mail.gmail.com> <8944597477930141639@unknownmsgid> <1a0793107537dceb9cc67c616294ce76@mail.gmail.com> <5132FE98.5050201@lerdorf.com> <513316A1.1050109@lerdorf.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQJ3DSuB//AVAgGgZEkT5WvLzC9oRwILJHjTAh6IVksCNX/beQFFG8MiAtbChFYB2/TX5AJ4t6N5AapYFrwBw9xHyAGd9UCHlqmhnAA= Date: Thu, 7 Mar 2013 18:06:50 +0200 Message-ID: <096465e9b4ef6d534f1b5d224ecb95d5@mail.gmail.com> To: Nikita Popov , Rasmus Lerdorf Cc: Pierre Joye , Laruence , PHP Developers Mailing List Content-Type: multipart/alternative; boundary=bcaec54ee1bc0853c204d757e504 X-Gm-Message-State: ALoCoQluJ+jgPpTpt+tdkM4Vy1YTEAvrxf3vGfBJIhR3iaYv7s8IdfNZPZ3U4B9vsDbFVDj4l/ky/8NVKjDHEdIlqt0+hSgG4SAlFXdgY4RN+SuYddU49DG1Zo6cpGDAzqPfeGaBC1sQ Subject: RE: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP distribution From: zeev@zend.com (Zeev Suraski) --bcaec54ee1bc0853c204d757e504 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Nikita, The 1-2 month estimation, is taken from about 50cm behind the fingers typing this email, aka my gut J. It=E2=80=99s quite possible it=E2=80=99ll= take much less, or no time at all; But it=E2=80=99s possible that once we include it, a lo= t more people test it, and we=E2=80=99ll get some feedback/requests/bugs that requ= ire attention and additional RC=E2=80=99s =E2=80=93 that we would otherwise not= have. Zeev *From:* Nikita Popov [mailto:nikita.ppv@gmail.com] *Sent:* Thursday, March 07, 2013 6:02 PM *To:* Rasmus Lerdorf *Cc:* Pierre Joye; Zeev Suraski; Laruence; PHP Developers Mailing List *Subject:* Re: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP distribution On Sun, Mar 3, 2013 at 10:23 AM, Rasmus Lerdorf wrote: On 03/03/2013 12:43 AM, Pierre Joye wrote: > On Sun, Mar 3, 2013 at 8:41 AM, Rasmus Lerdorf wrote= : >> The >> first step towards integration is getting it in. > > That does not guarantee that further steps can be done, from a timely manner. There is never any such guarantee and the current results of the vote clearly says that the majority of people are fine with a delayed 5.5 release. "The majority" yes. The accessors proposal also had "the majority" in favor, but that did not suffice. As of now this RFC does *not* have a 2/3 majority for the delay. And, as I already pointed out, I really think that this RFC should go by a 2/3 vote, as it is both a very large change AND a release delay. But regardless of that, could somebody maybe point out where the "it may require a 1-2 month delay" estimation in the RFC comes from? Somewhere Rasmus said that the integration will not be tight and just a "30 minute cleanup". I guess that was a bit exaggerated and may take a bit longer, but in the same order of magnitude (like 3 hours instead of 30 minutes). By that estimate the vote ends today and we can have ZO+ bundled in one or two days. To let the change sink a bit, fix a few bugs that turn up and figure out some questions like naming and default configuration one may need another week, or maybe two. Then we should already be able to go for a beta release. Everything else can be ironed out later (it's just a beta after all and after that we have a good bit of time to fix issues that turn up). Or did I miss something? Nikita --bcaec54ee1bc0853c204d757e504--