AZ>>Let me add to this: isn't this what "open source" is about? The bug AZ>>did not manifest itself on my system (FreeBSD). You pointed out the AZ>>issue. I fixed it. Cooperation prevailed. What's the big deal?
Well, the big deal is that sometimes - probably, not this time, but sometimes - "small changes" break things that the author didn't even think about it in some entirely different place. And it's always unexpected and unforeseen. That's why there's feature freeze period before release - and, talking about open source, each major open source project you look at - at least, each one I ever looked at - has it. This allows all the system as a whole to be sufficiently tested so that the chance that it is broken is small. If development code breaks, as you said - it's no big deal, you just fix it. But if released code gets broken, non-development people have to live with breakage until the next release. And living with broken version is much tougher than living without a feature. Especially when we talk about such a landmark release as 5.0.0. So I think it justifies some kind of "freeze paranoia" :) - if we don't have this and that feature 5.0.0 is still good and people would say "that's good and probably will be even better", but if it doesn't compile or doesn't work for someone - people would say "oh, that's a broken one, let us not use it". -- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
