Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65672
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain yahoo.de from 77.238.189.203 cause and error)
DomainKey-Status: good
DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=sg/mxv7LgixpG1V63VWAiVFhPVHw4afZPJLD8T8+AwvRlU7Y8TEqyiU3xUJsIfRhDN3B2sVuRQ9L9BNMH4BtEN7qbjveWcehkh1z/pdhZUZ57WdEUaAkq/oomLHz9/1SEEyIlpQ1RyAoVdK2jdKcLEY7DmXPAaI5z/KiottvIBs=;
References: <5d21b42656d49b4a71d9f808541bd745@mail.gmail.com> <1359562177.37091.YahooMailNeo@web133001.mail.ir2.yahoo.com> <1359562237.22084.YahooMailNeo@web133001.mail.ir2.yahoo.com> <a38a9590ac5c68c454b8340538a03690@mail.gmail.com>
Message-ID: <1360073623.83739.YahooMailNeo@web133006.mail.ir2.yahoo.com>
Date: Tue, 5 Feb 2013 14:13:43 +0000 (GMT)
Reply-To: hakre <hanskrentel@yahoo.de>
To: Zeev Suraski <zeev@zend.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
In-Reply-To: <a38a9590ac5c68c454b8340538a03690@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Integrating Zend Optimizer+ into the PHP distribution
From: hanskrentel@yahoo.de (hakre)

----- Urspr=C3=BCngliche Message -----=0A> Von: Zeev Suraski <zeev@zend.com=
>=0A> An: hakre <hanskrentel@yahoo.de>=0A> CC: internals@lists.php.net=0A> =
Gesendet: 17:47 Mittwoch, 30.Januar 2013=0A> Betreff: RE: [PHP-DEV] [RFC] I=
ntegrating Zend Optimizer+ into the PHP distribution=0A> =0A>>=C2=A0 > * In=
 that RFC you write:=0A>>=C2=A0 >=0A>>=C2=A0 > "the integration won=E2=80=
=99t happen before late 2014." [if =0A> it's not bundled=0A>>=C2=A0 > with =
PHP 5.5]=0A>>=C2=A0 >=0A>>=C2=A0 > Can you please outline why?=0A> =0A> Bas=
ed on an 18 month release cycle, and assuming we release 5.5.0 in mid=0A> 2=
013, 5.6.0 will come out late 2014.=0A=0AI wonder where you pick those quan=
tifications from, according to https://wiki.php.net/rfc/releaseprocess ther=
e is 12 month cycle/tact, and according to the release date of PHP =0A5.4 m=
ajor releases (golden) are scheduled for the first of march each =0Ayear (a=
lphas accordingly earlier).=0A=0A=0A>>=C2=A0 > * Which benefits does Zend I=
nc. see in contributing the Opcode cache?=0A> =0A> Simply put, this could b=
enefit PHP greatly without negatively affecting our=0A> business in any way=
.=0A=0AAnd not simply put?=0A=0A>>=C2=A0 > * Last but not least, not relate=
d to the opcode cache alone, but=0A>>=C2=A0 > related because you want to b=
undle it with core: If some day the PHP=0A>>=C2=A0 > group decides to choos=
e a similar software license, but different in=0A>>=C2=A0 > the sense that =
it is more compatible with existing FLOSS licensing,=0A>>=C2=A0 > would you=
 have a problem to re-license as well, e.g. under MIT or =0A> Apache=0A>>=
=C2=A0 > 2.0=0A>>=C2=A0 for that part?=0A> =0A> The plan is to contribute t=
he source code to the PHP project.=C2=A0 It'll be=0A> under the same licens=
e as PHP and subject to any changes in the PHP=0A> licensing scheme that we=
'll agree on.=0A=0AWho=0A is that "we" in the last sentence? Could copyrigh=
t be transfered to the=0A PHP group? Which developers so far did work on th=
at code? Do we get the=0A release history as well?=0A=0A-- hakre