Antony, > So this is the reason you think you can break the upcoming release now? > Please revert it, as I don't want to see yet another broken release > just because you decided you can do what you want. Instead of bothering me with your opinion have a look at my code and tell me where it is broken. Unless you find a bug this discussion is pointless. I seriously doubt that you will find anything, but try. We have completely different ideas about what "testing" means. Code commited by me usually WORKS. But that doesn't mean it is 100% bugfree and just because it seems to work doesn't mean I consider it 100% tested.
And spare me your believes that PHP developers commit to HEAD first and then backport to branches. This is a) not true and b) doesn't lead to not broken releases (Hello Zend) and c) doesn't solve the sync problem, because those working on HEAD often don't care at all about backporting. This has happened f.e. a bunch of times with security patches that were never backported from HEAD. When I say I will take care of later merging the new code into HEAD when I am 100%ly sure that there is no obvious bug left, then I will do that. I see no point in reverting the code. If you fear that it breaks an upcoming release then simply install PHP 5.2 and try uploading files. Wait.... that would be a too easy check and you would not be able to flame... (Wait... the same check would have catched the Zend fault in 5.1.3...) Stefan -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
