# O+ - are we ready to go ahead and vote?

- Thread: https://externals.io/message/66268
- Original archive: https://news-web.php.net/php.internals/66268
- Started by Zeev Suraski on 2013-02-27T11:06:03+00:00
- Messages: 9
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #66268 — Zeev Suraski — 2013-02-27T11:06:03+00:00

URL: https://externals.io/message/66268#66268

Are there any additional clarifications and/or unanswered questions people
are still waiting for, or can we move ahead to vote on the O+ inclusion RFC?



Zeev

---

## #66273 — Sara Golemon — 2013-02-27T15:19:04+00:00

URL: https://externals.io/message/66268#66273 · In reply to: #66268

> Are there any additional clarifications and/or unanswered questions people
> are still waiting for, or can we move ahead to vote on the O+ inclusion RFC?
>
It's been nearly a month since the RFC was posted and there's been
little-to-no discussion in the past week, I'd say it's ready to vote
on...

-Sara

---

## #66288 — Pierre Joye — 2013-02-27T19:04:04+00:00

URL: https://externals.io/message/66268#66288 · In reply to: #66268

hi Zeev,


> Are there any additional clarifications and/or unanswered questions people
> are still waiting for, or can we move ahead to vote on the O+ inclusion RFC?

I have mixed feelings.

On one side I would say go ahead! But on the other side I've some worries.

We discussed about 1st having in pecl, there is no release yet and
this is something so easy and fast to do. I wonder why it was not
done.

There is also a couple of bugs (most of them seem to fixed but more
testing are required). Once they are valid we can go for a wilder
range of tests as these bugs simply prevent us to run many of the use
cases. More on these cases later this week/early next week.

But you moved to vote already, so it is barely pointless to argue or?
I'd to get it in PECL as well, or even prior to any move to core.

Cheers,
-- 
Pierre

@pierrejoye

---

## #66290 — Christopher Jones — 2013-02-27T19:05:43+00:00

URL: https://externals.io/message/66268#66290 · In reply to: #66268

> Are there any additional clarifications and/or unanswered questions people
> are still waiting for, or can we move ahead to vote on the O+ inclusion RFC?
>
>
>
> Zeev
>

Are there any updated guesstimates at how long integration into PHP 5.5 will take?

Chris

-- 
christopher.jones@oracle.com  http://twitter.com/ghrd
Newly updated, free PHP & Oracle book:
http://www.oracle.com/technetwork/topics/php/underground-php-oracle-manual-098250.html

---

## #66291 — Remi Collet — 2013-02-27T19:12:50+00:00

URL: https://externals.io/message/66268#66291 · In reply to: #66288

Le 27/02/2013 20:04, Pierre Joye a écrit :

> I'd to get it in PECL as well, or even prior to any move to core.

+1

It will give php 5.4 (and 5.3) users an alternative to APC and will give
more audience to this extension (so more tests / feedback)


Remi.

---

## #66292 — Pierre Joye — 2013-02-27T19:26:10+00:00

URL: https://externals.io/message/66268#66292 · In reply to: #66290

On Wed, Feb 27, 2013 at 8:05 PM, Christopher Jones
<christopher.jones@oracle.com> wrote:

> Are there any updated guesstimates at how long integration into PHP 5.5 will
> take?

There will be no integration, but the idea is to bundle it, as it is.
The actual integration is a large task and should/will target 5.6 and
later.

Or do you mean the tests&fixes sessions to get it work out of the box?

Cheers,
-- 
Pierre

@pierrejoye

---

## #66293 — Rasmus Lerdorf — 2013-02-27T19:31:16+00:00

URL: https://externals.io/message/66268#66293 · In reply to: #66292

> On Wed, Feb 27, 2013 at 8:05 PM, Christopher Jones
> <christopher.jones@oracle.com> wrote:
> 
> > […]
> 
> There will be no integration, but the idea is to bundle it, as it is.
> The actual integration is a large task and should/will target 5.6 and
> later.

That's not true, there will be some. When bundling it with 5.5 we can
remove the ifdefs and extra code only needed for prior versions, for
example, and we should rename the ini names and such. So simple
30-minute cleanup type of stuff, but yes, deep integration with the
compiler and executor will be left for later.

-Rasmus

---

## #66296 — Christopher Jones — 2013-02-27T19:34:10+00:00

URL: https://externals.io/message/66268#66296 · In reply to: #66292

> On Wed, Feb 27, 2013 at 8:05 PM, Christopher Jones
> <christopher.jones@oracle.com> wrote:
>
> > […]
>
> There will be no integration, but the idea is to bundle it, as it is.
> The actual integration is a large task and should/will target 5.6 and
> later.
>
> Or do you mean the tests&fixes sessions to get it work out of the box?
>
> Cheers,
>

The three voting options all use the word "integrate". In a previous
email, Zeev clarified what it means: "By integration I refer to
including something that is production quality, potentially
enabled-by-default (TBD), that everyone should feel comfortable
using."

Chris

-- 
christopher.jones@oracle.com  http://twitter.com/ghrd
Newly updated, free PHP & Oracle book:
http://www.oracle.com/technetwork/topics/php/underground-php-oracle-manual-098250.html

---

## #66297 — Pierre Joye — 2013-02-27T20:04:05+00:00

URL: https://externals.io/message/66268#66297 · In reply to: #66293

> That's not true, there will be some. When bundling it with 5.5 we can
> remove the ifdefs and extra code only needed for prior versions, for
> example, and we should rename the ini names and such.

I called that cleanup not integration, but that's nitpicking :)

> So simple
> 30-minute cleanup type of stuff, but yes, deep integration with the
> compiler and executor will be left for later.

Indeed.

Cheers,
-- 
Pierre

@pierrejoye
