# PHP 5.2.10 - Thread: https://externals.io/message/43929 - Original archive: https://news-web.php.net/php.internals/43929 - Started by Ilia Alshanetsky on 2009-05-14T16:21:53+00:00 - Messages: 24 - 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 --- ## #43929 — Ilia Alshanetsky — 2009-05-14T16:21:53+00:00 URL: https://externals.io/message/43929#43929 We have a fair number of fixes in the 5.2 branch already and while 5.3 is making very good progress I think it is still ways off in terms of final release and stabilization. I think it makes sense to do one more 5.2 release before 5.3 is out and 5.2 can be discontinued. I would like to roll an RC1 by May 28th, so please get your fixes in. Thanks, Ilia Alshanetsky 5.2 Release Master --- ## #43930 — Lester Caine — 2009-05-14T16:45:25+00:00 URL: https://externals.io/message/43929#43930 · In reply to: #43929 Ilia Alshanetsky wrote: > We have a fair number of fixes in the 5.2 branch already and while 5.3 > is making very good progress I think it is still ways off in terms of > final release and stabilization. I think it makes sense to do one more > 5.2 release before 5.3 is out and 5.2 can be discontinued. I would like > to roll an RC1 by May 28th, so please get your fixes in. Since 5.3 DOES require some work to port legacy applications over PLEASE do not discontinue 5.2 security fixes until 5.3 has bedded down ( remember 5.1 ... ) -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php --- ## #43931 — Hannes Magnusson — 2009-05-14T16:51:53+00:00 URL: https://externals.io/message/43929#43931 · In reply to: #43930 > Ilia Alshanetsky wrote: > > […] > > Since 5.3 DOES require some work to port legacy applications over Do you have a quick list of things that is required so we can document them, or maybe even fix? -Hannes --- ## #43933 — Pierre Joye — 2009-05-14T17:05:36+00:00 URL: https://externals.io/message/43929#43933 · In reply to: #43929 Hi, > We have a fair number of fixes in the 5.2 branch already and while 5.3 is > making very good progress I think it is still ways off in terms of final > release and stabilization. I think it makes sense to do one more 5.2 release > before 5.3 is out and 5.2 can be discontinued. I would like to roll an RC1 > by May 28th, so please get your fixes in. Thanks for the notice! End of the month for the RC1 is perfect. About discontinuing 5.2, it may be too early to decide. Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org --- ## #43934 — Michael Shadle — 2009-05-14T17:09:47+00:00 URL: https://externals.io/message/43929#43934 · In reply to: #43933 > Hi, > > > > […] > > Thanks for the notice! End of the month for the RC1 is perfect. > > About discontinuing 5.2, it may be too early to decide. This makes me a little sad - I was thinking PHP 5.3 was closer to production. --- ## #43937 — Guilherme Blanco — 2009-05-14T17:37:22+00:00 URL: https://externals.io/message/43929#43937 · In reply to: #43934 IMHO, 5.2 should be stopped as soon as 5.3.0 is released. > > > […] > > This makes me a little sad - I was thinking PHP 5.3 was closer to production. > > -- > > > > -- Guilherme Blanco - Web Developer CBC - Certified Bindows Consultant Cell Phone: +55 (16) 9215-8480 MSN: guilhermeblanco@hotmail.com URL: http://blog.bisna.com São Paulo - SP/Brazil --- ## #43938 — Andrei Zmievski — 2009-05-14T17:39:42+00:00 URL: https://externals.io/message/43929#43938 · In reply to: #43929 Ilia Alshanetsky wrote: > We have a fair number of fixes in the 5.2 branch already and while 5.3 > is making very good progress I think it is still ways off in terms of > final release and stabilization. I think it makes sense to do one more > 5.2 release before 5.3 is out and 5.2 can be discontinued. I would like > to roll an RC1 by May 28th, so please get your fixes in. I would really like to make a patch to ext/json to expose the encoding/decoding functions so that they can be called from other extensions. I should be able to wrap this up in the next few days. -Andrei --- ## #43942 — Ilia Alshanetsky — 2009-05-14T18:10:02+00:00 URL: https://externals.io/message/43929#43942 · In reply to: #43938 This is a new feature, so it would be more appropriate for 5.3/6 more so then for 5.2 IMHO. Ilia Alshanetsky > Ilia Alshanetsky wrote: > > […] > > I would really like to make a patch to ext/json to expose the > encoding/decoding functions so that they can be called from other > extensions. I should be able to wrap this up in the next few days. > > -Andrei --- ## #43944 — Andrei Zmievski — 2009-05-14T18:36:14+00:00 URL: https://externals.io/message/43929#43944 · In reply to: #43942 It doesn't impact anything though, does it? And it would really help for implementing json-based serializers (such as for memcached). -Andrei Ilia Alshanetsky wrote: > This is a new feature, so it would be more appropriate for 5.3/6 more so > then for 5.2 IMHO. > > Ilia Alshanetsky > > > > > > > > […] --- ## #43946 — Jani Taskinen — 2009-05-14T18:47:10+00:00 URL: https://externals.io/message/43929#43946 · In reply to: #43944 It's still new stuff. And we need more things in 5.3/6 to make them more interesting to general populus too. ;) --Jani Andrei Zmievski kirjoitti: > It doesn't impact anything though, does it? And it would really help for > implementing json-based serializers (such as for memcached). > > -Andrei > > Ilia Alshanetsky wrote: > > […] --- ## #43947 — Jani Taskinen — 2009-05-14T18:49:43+00:00 URL: https://externals.io/message/43929#43947 · In reply to: #43929 Ilia Alshanetsky kirjoitti: > We have a fair number of fixes in the 5.2 branch already and while 5.3 > is making very good progress I think it is still ways off in terms of > final release and stabilization. I think it makes sense to do one more > 5.2 release before 5.3 is out and 5.2 can be discontinued. I would like > to roll an RC1 by May 28th, so please get your fixes in. Can we add some sort of notice to that release, something like this: "If you did not test a release candidate, any bug report send about issue introduced in this release will automatically be bogus." ?? :D --Jani --- ## #43948 — Andrei Zmievski — 2009-05-14T18:54:49+00:00 URL: https://externals.io/message/43929#43948 · In reply to: #43946 Jani Taskinen wrote: > It's still new stuff. And we need more things in 5.3/6 to make them more > interesting to general populus too. ;) Great, so I'll just end up copying almost all of ext/json code into pecl/memcached then. Hooray for loose coupling. -Andrei --- ## #43949 — Ilia Alshanetsky — 2009-05-14T18:55:26+00:00 URL: https://externals.io/message/43929#43949 · In reply to: #43947 Maybe only allow people who ran make test and submitted the results during the RC phase to submit bugs, eh? ;-) Ilia Alshanetsky > Ilia Alshanetsky kirjoitti: > > […] > > Can we add some sort of notice to that release, something like this: > > "If you did not test a release candidate, any bug report send about > issue introduced in this release will automatically be bogus." ?? :D > > --Jani --- ## #43951 — Ilia Alshanetsky — 2009-05-14T19:01:05+00:00 URL: https://externals.io/message/43929#43951 · In reply to: #43948 Andrei, There is no question about functionality being useful for some people. But what is the point of different branches if we put whatever we want into each branch? We may as well stick to one branch and commit features, bug fixes, etc... into it. Ilia Alshanetsky > Jani Taskinen wrote: > > […] > > Great, so I'll just end up copying almost all of ext/json code into > pecl/memcached then. Hooray for loose coupling. > > -Andrei --- ## #43954 — Lester Caine — 2009-05-14T19:25:39+00:00 URL: https://externals.io/message/43929#43954 · In reply to: #43931 Hannes Magnusson wrote: > > > […] > > Do you have a quick list of things that is required so we can document > them, or maybe even fix? Several hundred warnings that are not present currently? The code base has not YET dropped PHP4 compatibility, so a PHP5 only build may be required to 'tidy things up' .... and we are not able as yet to do THAT :( -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php --- ## #43956 — Pierre Joye — 2009-05-14T20:04:36+00:00 URL: https://externals.io/message/43929#43956 · In reply to: #43948 hi Ilia, > Jani Taskinen wrote: > > […] > > Great, so I'll just end up copying almost all of ext/json code into > pecl/memcached then. Hooray for loose coupling. It is actually not about adding features. If I understand correctly what Andrei likes to have, it is only about exposing the JSON API. That means no code change (no new feature or whatever else) but only adding the right PHP_API related declaration to the right place and install the json header. That could actually be very useful with no impact on the code (userland or extensions). I think we should allow this change. Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org --- ## #43957 — Andrei Zmievski — 2009-05-14T20:07:42+00:00 URL: https://externals.io/message/43929#43957 · In reply to: #43951 Ilia Alshanetsky wrote: > Andrei, > > There is no question about functionality being useful for some people. > But what is the point of different branches if we put whatever we want > into each branch? We may as well stick to one branch and commit > features, bug fixes, etc... into it. I would fully agree with you if this concerned a user-visible API change or a new feature. But this is simply exposing a couple of internal functions so that they are visible from other extensions, and, arguably, something that should have been done properly from the beginning. -Andrei --- ## #43958 — Ilia Alshanetsky — 2009-05-14T20:09:03+00:00 URL: https://externals.io/message/43929#43958 · In reply to: #43956 If we are simply changing the declaration that should be fine, is there a patch available for review? Ilia Alshanetsky > hi Ilia, > > On Thu, May 14, 2009 at 8:54 PM, Andrei Zmievski > […] > > It is actually not about adding features. If I understand correctly > what Andrei likes to have, it is only about exposing the JSON API. > That means no code change (no new feature or whatever else) but only > adding the right PHP_API related declaration to the right place and > install the json header. That could actually be very useful with no > impact on the code (userland or extensions). > > I think we should allow this change. > > Cheers, > -- > Pierre > > http://blog.thepimp.net | http://www.libgd.org --- ## #43960 — Andrei Zmievski — 2009-05-14T20:11:20+00:00 URL: https://externals.io/message/43929#43960 · In reply to: #43958 Not yet. It's a simple declaration change for json_encode_r(), but `json_decode()` doesn't have json_decode_r(), so we'd need to create it from the guts of `json_decode()`. -Andrei Ilia Alshanetsky wrote: > If we are simply changing the declaration that should be fine, is there > a patch available for review? > > > Ilia Alshanetsky > > > > > > > > […] --- ## #43962 — Stanislav Malyshev — 2009-05-14T20:26:01+00:00 URL: https://externals.io/message/43929#43962 · In reply to: #43929 Hi! > We have a fair number of fixes in the 5.2 branch already and while 5.3 > is making very good progress I think it is still ways off in terms of > final release and stabilization. I think it makes sense to do one more > 5.2 release before 5.3 is out and 5.2 can be discontinued. I would like > to roll an RC1 by May 28th, so please get your fixes in. I think 5.2 should still be alive for security/critical fixes at least until we are sure 5.3 is tested enough in the field. -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com --- ## #43971 — Hannes Magnusson — 2009-05-15T07:12:57+00:00 URL: https://externals.io/message/43929#43971 · In reply to: #43954 > Hannes Magnusson wrote: > > […] > > Several hundred warnings that are not present currently? Please be more precise. -Hannes --- ## #43981 — Lester Caine — 2009-05-15T09:13:03+00:00 URL: https://externals.io/message/43929#43981 · In reply to: #43971 Sorry Hannes - forgot to change To address! Hannes Magnusson wrote: > > > […] > > Please be more precise. I would like to be, but having downloaded RC2 clean and had a look we still have the major blocker of not having php_interbase.dll in the windows build - so I'm unable to run any of my test stuff ... I don't currently have a Linux box spare to try on that :( -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php --- ## #43995 — Giovanni Giacobbi — 2009-05-15T17:50:14+00:00 URL: https://externals.io/message/43929#43995 · In reply to: #43956 > hi Ilia, > > > > […] > > It is actually not about adding features. If I understand correctly > what Andrei likes to have, it is only about exposing the JSON API. > That means no code change (no new feature or whatever else) but only > adding the right PHP_API related declaration to the right place and > install the json header. That could actually be very useful with no > impact on the code (userland or extensions). > > I think we should allow this change. > Sorry if I'm not getting this right, but doesn't he have to explicitly require version >= 5.2.10 in his pecl/memcached extension? It's not like that with this change his extension is going to work for 5.2.x. Requiring >= 5.2.10 is such a strict requirement that should be replaced with >= 5.3.0. -- Giovanni Giacobbi --- ## #43996 — Scott MacVicar — 2009-05-15T17:53:21+00:00 URL: https://externals.io/message/43929#43996 · In reply to: #43995 Giovanni Giacobbi wrote: > > > […] > > Sorry if I'm not getting this right, but doesn't he have to explicitly require version >= 5.2.10 in his pecl/memcached extension? It's not like that with this change his extension is going to work for 5.2.x. Requiring >= 5.2.10 is such a strict requirement that should be replaced with >= 5.3.0. > You can use call_user_func_ex() internally to call it, it's nicer to use the C API though. Though this is the wrong place to ask. Scott