hi, On Fri, Jan 2, 2009 at 2:59 PM, Lukas Kahwe Smith <m...@pooteeweet.org> wrote:
> @Marcus: Like I said its a question of someone writing the code .. Timm > proposed a patch which Stas thought had issues and then nobody picked things > up .. > > @Pierre/all: Well we did announce something like a freeze. Of course there > are still changes going in undiscussed and for the most part this is ok (and > not doing those changes would be a bad idea and unnecessary to be delayed). > However I would really appreciate it if people would really think about the > changes they are doing. Think twice about changes that can introduce a > regression or a lot of work and ask if the change has any change of being > problematic. We all agree here, maybe not being too strict when it comes to extensions. Breakages in an ext can be reverted at any stage (almost any). > In this light the dl() change by Marcus (AFAIK this was planned and done for > 6.0 and not 5.3) and the windows PCRE change by Andi seem potential > candidates for regressions, issues and maybe should have been discussed > beforehand. Just using these two has an example since they are the two last > commits I marked as potential issues. If we can't test such changes in the current release phase, then we will never be able to do anything sane. Alpha releases are mainly marketing releases, if I can say so. Only very few actually tests them in comparison to beta or RC. About the dl issue, I think it is a good idea to drop it in 5.3. It never worked anyway and causes all kind of side effects (the worst being segv). However, it would have been preferable to post a little note on internals before, for the principle :) > BTW: I was planning on sending out a mail on Monday about beta1. Johannes > and I feel like a release on the 20th or 22nd seems realistic. Sounds fine for me too. Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
