# Last steps towards 5.3.0 - Thread: https://externals.io/message/44212 - Original archive: https://news-web.php.net/php.internals/44212 - Started by johannes@php.net on 2009-06-10T14:43:32+00:00 - Messages: 13 - 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 --- ## #44212 — johannes@php.net — 2009-06-10T14:43:32+00:00 URL: https://externals.io/message/44212#44212 Hi, it was a long run so far and it's time to really take the last steps to get the beast out. For this Lukas and I decided on the following plan: June 10th (today): We package RC3, until then only critical build fixes and similar which have to go in the RC, after review (highlight me on IRC, mail etc.) June 11th: RC3 will be released June 11th-17th A small window for critical fixes and again please check beforehand as we don't want to introduce any new bugs that late in the game. June 17th In case there were commits after RC3 we will package a RC 4 on Wednesday next week June 18th If needed publish RC4 June 18th - June 24th The plan is to repackage RC4 as 5.3.0 final in the beginning of the week of the 21st without any further changes so we can test the packages. In case something critical, unexpected, pops up please notify us asap. June 25th 2009 Release PHP 5.3.0 final. We hope this works out as planned and are excited to finally being close to the release. Lukas and Johannes --- ## #44214 — Guilherme Blanco — 2009-06-10T15:14:44+00:00 URL: https://externals.io/message/44212#44214 · In reply to: #44212 Just 2 questions.... 1- Will it include new autoloader definition that standards group was talking about? 2- I still have a BC break that I cannot isolate (huge codebase). I'm trying to find it and once I isolate it and report, will the fix be included before 5.3.0 final? PS: If someone wants to give a hand to find the regression... I can explain how to reproduce. Regards, 2009/6/10 Johannes Schlüter : > Hi, > > it was a long run so far and it's time to really take the last steps to > get the beast out. > > For this Lukas and I decided on the following plan: > > June 10th (today): >  We package RC3, until then only critical >  build fixes and similar which have to go in the RC, after review >  (highlight me on IRC, mail etc.) > > June 11th: >  RC3 will be released > > June 11th-17th >  A small window for critical fixes and again please check beforehand as >  we don't want to introduce any new bugs that late in the game. > > June 17th >  In case there were commits after RC3 we will package a RC 4 on >  Wednesday next week > > June 18th >  If needed publish RC4 > > June 18th - June 24th >  The plan is to repackage RC4 as 5.3.0 final in the beginning of the >  week of the 21st without any further changes so we can test the >  packages. In case something critical, unexpected, pops up please >  notify us asap. > > June 25th 2009 >  Release PHP 5.3.0 final. > > > We hope this works out as planned and are excited to finally being close > to the release. > > Lukas and Johannes > > > -- > > > > -- 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 --- ## #44215 — Greg Beaver — 2009-06-10T15:33:27+00:00 URL: https://externals.io/message/44212#44215 · In reply to: #44214 Guilherme Blanco wrote: > Just 2 questions.... > > 1- Will it include new autoloader definition that standards group was > talking about? Hi, I am not an official RM representative, the following is my opinion: Not the slightest chance. It hasn't even been suggested to internals yet and additionally qualifies as a new feature, so it was a pipe dream of the group in question that it would get into 5.3. Greg --- ## #44217 — Lukas Kahwe Smith — 2009-06-10T15:38:02+00:00 URL: https://externals.io/message/44212#44217 · In reply to: #44215 > Guilherme Blanco wrote: > > […] no .. there was no proposal, therefore no discussion, therefore its not going to be included, since we are long past adding new features. regards, Lukas Kahwe Smith mls@pooteeweet.org --- ## #44218 — Guilherme Blanco — 2009-06-10T15:39:43+00:00 URL: https://externals.io/message/44212#44218 · In reply to: #44215 Greg, I joined the standards group last week. It seems they already have a patch but it was not yet officially proposed because none reached a common agreement yet. Group switched with PEAR style of proposal and voting. So anyone can propose new inclusions. The patch is actually just a direct check to folder /vendor/PackageName.... But ok, thanks for the clean answer. =) 2009/6/10 Greg Beaver : > Guilherme Blanco wrote: > > […] > > Hi, > > I am not an official RM representative, the following is my opinion: > > Not the slightest chance.  It hasn't even been suggested to internals > yet and additionally qualifies as a new feature, so it was a pipe dream > of the group in question that it would get into 5.3. > > Greg > -- 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 --- ## #44220 — johannes@php.net — 2009-06-10T16:21:29+00:00 URL: https://externals.io/message/44212#44220 · In reply to: #44214 Hi, > 1- Will it include new autoloader definition that standards group was > talking about? No proposal, no code, ... > 2- I still have a BC break that I cannot isolate (huge codebase). I'm > trying to find it and once I isolate it and report, will the fix be > included before 5.3.0 final? Maybe. Everything else depends on the case and can't be said in a generic way. The overall goal is not to have too many BC issues - besides lot's of deprecation warnings the only real problem I ever found in multiple applications was related to `call_user_func_array()` in combination with bad usage of references, but that one hit a few projects I saw. johannes --- ## #44227 — Lukas Kahwe Smith — 2009-06-10T19:07:28+00:00 URL: https://externals.io/message/44212#44227 · In reply to: #44212 > Hi, > > it was a long run so far and it's time to really take the last steps > to > get the beast out. > > For this Lukas and I decided on the following plan: > > June 10th (today): > We package RC3, until then only critical > build fixes and similar which have to go in the RC, after review > (highlight me on IRC, mail etc.) ok this step is completed > June 11th: > RC3 will be released > > June 11th-17th > A small window for critical fixes and again please check beforehand > as > we don't want to introduce any new bugs that late in the game. Ok, we are out of commit freeze. @Ilia: go ahead and merge your fix for #48512 @Tony: you can now apply that curl arginfo patch and the fix for the curl crash @Pierre: you can now also apply the patches you were looking to commit @Hannes: I guess we will wait until Johannes has determined if the patch is really necessary @Andrey: I guess you will/have talked to Johannes about your patches regards, Lukas Kahwe Smith mls@pooteeweet.org --- ## #44228 — Nuno Lopes — 2009-06-10T20:38:41+00:00 URL: https://externals.io/message/44212#44228 · In reply to: #44214 > PS: If someone wants to give a hand to find the regression... I can > explain how to reproduce. The easiest way is to use a tool to help reducing the test case automatically. I don't know about any specific tool for reducing PHP files, but in the past I've used delta (http://delta.tigris.org/), which is a reducer for C/C++ and it works quite well with PHP. You have to do two things in order it to work: disable topformflat (because it doesn't understand PHP), and inline the included files after the first reduction step, and keep inlining the include()'s that survive to a reduce step. Nevertheless, it's a fairly trivial process. Nuno --- ## #44229 — Paul Biggar — 2009-06-10T22:10:17+00:00 URL: https://externals.io/message/44212#44229 · In reply to: #44228 Hi Guilherme, Nuno, > > […] > > The easiest way is to use a tool to help reducing the test case > automatically. > I don't know about any specific tool for reducing PHP files, but in the past I wrote a tool which automatically. It uses the delta debugging algorithm, but is very much faster than delta, since it knows how PHP works. I hope its also easier to use - you basically write a function which takes source code, and returns true if the bug is still present. Its at http://code.google.com/p/phc/source/browse/trunk/test/framework/reduce/Reduce.php. You need to a copy of phc (phpcompiler.org) as well. The usage is explained in the comments. I've used it a lot, but I've only just made it work more generally. Please report any problems to me. Paul -- Paul Biggar paul.biggar@gmail.com --- ## #44231 — Paul Biggar — 2009-06-10T22:12:50+00:00 URL: https://externals.io/message/44212#44231 · In reply to: #44229 > I wrote a tool which automatically. It uses the delta debugging I sent this prematurely. It should read "I wrote a tool which reduces test cases automatically." > algorithm, but is very much faster than delta, since it knows how PHP > works. I hope its also easier to use - you basically write a function > which takes source code, and returns true if the bug is still present. > > Its at http://code.google.com/p/phc/source/browse/trunk/test/framework/reduce/Reduce.php. > You need to a copy of phc (phpcompiler.org) as well. The usage is > explained in the comments. I've used it a lot, but I've only just made > it work more generally. Please report any problems to me. > > > Paul > > > -- > Paul Biggar > paul.biggar@gmail.com > -- Paul Biggar paul.biggar@gmail.com --- ## #44239 — Nuno Lopes — 2009-06-11T08:35:35+00:00 URL: https://externals.io/message/44212#44239 · In reply to: #44229 > > > […] > > > I wrote a tool which automatically. It uses the delta debugging > algorithm, but is very much faster than delta, since it knows how PHP > works. I hope its also easier to use - you basically write a function > which takes source code, and returns true if the bug is still present. > > Its at > http://code.google.com/p/phc/source/browse/trunk/test/framework/reduce/Reduce.php. > You need to a copy of phc (phpcompiler.org) as well. The usage is > explained in the comments. I've used it a lot, but I've only just made > it work more generally. Please report any problems to me. Oh, very nice, Paul ;) I wasn't aware of this script. btw, does it perform inlining of included files? (so that you can have a self-contained reduced file) Nuno --- ## #44241 — Paul Biggar — 2009-06-11T09:40:33+00:00 URL: https://externals.io/message/44212#44241 · In reply to: #44239 > Oh, very nice, Paul ;) I wasn't aware of this script. > btw, does it perform inlining of included files? (so that you can have a > self-contained reduced file) phc supporting inlining with --include. So I would guess that calling $reduce->set_phc ("phc --include") it would work, but I haven't tried it. Paul -- Paul Biggar paul.biggar@gmail.com --- ## #44294 — Lukas Kahwe Smith — 2009-06-16T07:55:09+00:00 URL: https://externals.io/message/44212#44294 · In reply to: #44212 > June 10th (today): > We package RC3, until then only critical > build fixes and similar which have to go in the RC, after review > (highlight me on IRC, mail etc.) > > June 11th: > RC3 will be released > > June 11th-17th > A small window for critical fixes and again please check beforehand > as > we don't want to introduce any new bugs that late in the game. > > June 17th > In case there were commits after RC3 we will package a RC 4 on > Wednesday next week Ok, we are here now. So we are in a commit freeze as of this morning until sometime Wednesday. When we have tagged RC4, please only commit to 5_3 with the explicit blessing of Johannes until we release 5_3 stable or announce an extension of the RC phase. So far I want to get clarification on how set_magic_quotes_runtime(0) behaves in PHP6. I also talked to Pierre about the late changes in windows (which Johannes and I were aware of since weeks). Its clear that this change will not hold up any releases. Pierre will revert if necessary. > June 18th > If needed publish RC4 > > June 18th - June 24th > The plan is to repackage RC4 as 5.3.0 final in the beginning of the > week of the 21st without any further changes so we can test the > packages. In case something critical, unexpected, pops up please > notify us asap. > > June 25th 2009 > Release PHP 5.3.0 final. We are still on track for this one. regards, Lukas Kahwe Smith mls@pooteeweet.org