At what point is O+ reporting going to be possible through
https://bugs.php.net/ ?
I realize that this is a bit of a catch-22, but surely it would be
better to allow properly tracked open bug reporting sooner rather later?
Regards Terry
Having it in peck right now allows that. But as of now it is not a PHP.net
project so it makes little sense to have it listed there.
At what point is O+ reporting going to be possible through
https://bugs.php.net/ ?I realize that this is a bit of a catch-22, but surely it would be better
to allow properly tracked open bug reporting sooner rather later?Regards Terry
>
> Having it in peck right now allows that. But as of now it is not a
> PHP.net project so it makes little sense to have it listed there.
>
> On Mar 2, 2013 10:33 AM, "Terry Ellison"
>
> At what point is O+ reporting going to be possible through
> https://bugs.php.net/ ?
>
> I realize that this is a bit of a catch-22, but surely it would be
> better to allow properly tracked open bug reporting sooner rather
> later?
>
Thanks Pierre, I understand and that's why I mentioned catch-22. AFAIK,
there's no open bug and issue reporting available prior to its formal
adoption, event though we all realize that it's going to be pretty much
inevitable -- for compelling reasons -- and by the time it is adopted
the first release will be a fait accompli.
>
>>
>> Having it in peck right now allows that. But as of now it is not a PHP.net project so it makes little sense to have it listed there.
>>
>>
>>
>> At what point is O+ reporting going to be possible through
>> https://bugs.php.net/ ?
>>
>> I realize that this is a bit of a catch-22, but surely it would be
>> better to allow properly tracked open bug reporting sooner rather
>> later?
>>
>
> Thanks Pierre, I understand and that's why I mentioned catch-22. AFAIK, there's no open bug and issue reporting available prior to its formal
> adoption, event though we all realize that it's going to be pretty much inevitable -- for compelling reasons -- and by the time it is adopted the
> first release will be a fait accompli.
>
Bugs can (and have been) reported via https://github.com/zend-dev/ZendOptimizerPlus/issues
I'm sure email reports will also do fine in the interim.
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
>
>>> I realize that this is a bit of a catch-22, but surely it would be
>>> better to allow properly tracked open bug reporting sooner rather
>>> later?
>>>
>>
> Bugs can (and have been) reported via
> https://github.com/zend-dev/ZendOptimizerPlus/issues
> I'm sure email reports will also do fine in the interim.
>
I guess this is a case of "Durrrr, my bad". Zeev gave the github URI in
his initial announcement. I should have done a 1+1 ...
Thanks Chris, sometimes an =2 is very useful :oops;
//Terry
Christopher Jones in php.internals (Sat, 02 Mar 2013 09:42:30 -0800):
Bugs can (and have been) reported via https://github.com/zend-dev/ZendOptimizerPlus/issues
Just to draw the attention on the list:
https://github.com/zend-dev/ZendOptimizerPlus/issues/57
O+ is not stable yet, it does not even pass some tests reliably:
https://github.com/zend-dev/ZendOptimizerPlus/issues/59
The latter one is by a co-worker of Pierre, #57 by me. I am getting the
impression serious testing by users has yet to begin.
Jan
>
>
>
>>
>>>
>>> Having it in peck right now allows that. But as of now it is not a PHP.net project so it makes little sense to have it listed there.
>>>
>>>
>>>
>>> At what point is O+ reporting going to be possible through
>>> https://bugs.php.net/ ?
>>>
>>> I realize that this is a bit of a catch-22, but surely it would be
>>> better to allow properly tracked open bug reporting sooner rather
>>> later?
>>>
>>
>> Thanks Pierre, I understand and that's why I mentioned catch-22. AFAIK, there's no open bug and issue reporting available prior to its formal
>> adoption, event though we all realize that it's going to be pretty much inevitable -- for compelling reasons -- and by the time it is adopted the
>> first release will be a fait accompli.
>>
>
> Bugs can (and have been) reported via https://github.com/zend-dev/ZendOptimizerPlus/issues
> I'm sure email reports will also do fine in the interim.
>
> Chris
>
Felipe added ZO+ to the bugs.php.net "Package affected" drop-down today.
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
>
>
>
>>
>>
>>
>>
>>>
>>>
>>>>
>>>>
>>>> Having it in peck right now allows that. But as of now it is not a
>>>> PHP.net project so it makes little sense to have it listed there.
>>>>
>>>> On Mar 2, 2013 10:33 AM, "Terry Ellison"
>>>>
>>>> At what point is O+ reporting going to be possible through
>>>> https://bugs.php.net/ ?
>>>>
>>>> I realize that this is a bit of a catch-22, but surely it would be
>>>> better to allow properly tracked open bug reporting sooner rather
>>>> later?
>>>>
>>>
>>> Thanks Pierre, I understand and that's why I mentioned catch-22. AFAIK,
>>> there's no open bug and issue reporting available prior to its formal
>>> adoption, event though we all realize that it's going to be pretty much
>>> inevitable -- for compelling reasons -- and by the time it is adopted the
>>> first release will be a fait accompli.
>>>
>>
>> Bugs can (and have been) reported via
>> https://github.com/zend-dev/ZendOptimizerPlus/issues
>> I'm sure email reports will also do fine in the interim.
>>
>> Chris
>>
>
> Felipe added ZO+ to the bugs.php.net "Package affected" drop-down today.
>
Hmmh.. That shouldn't be there as the current official issue tracker
for it is on github, and is linked from the pecl page..
Once it gets merged into php-src then that package should be created though.
-Hannes
Felipe added ZO+ to the bugs.php.net "Package affected" drop-down today.
Hmmh.. That shouldn't be there as the current official issue tracker
for it is on github, and is linked from the pecl page..
Only since a day or two - there is no reason why we can't have it in our
normal bug tracker as the extension is going to be part of that very
soon anyway.
cheers,
Derick