Due to the nature of my work, I have encountered just about every imaginable bug in the build process, if I were to submit bug reports on each and every issue encountered, the number alone would swamp the developers who spend their time validating and substantiating the reported bugs because I am not your average yogi bear.
I think you need not to worry about swamping developers. If all of the issues are real bugs, the developers would find time - now or in the future - to fix them. Even if they do not - either because nobody considered it important or some other reason - the issue would still be known and waiting for somebody to fix it, eventually. That's the power of open source development model. I understand that having to encounter a lot of bugs can be frustrating, and it can happen if you venture to do something that not many have done before. The best way to deal with it is to contribute a little amount of your time on filing bug reports, thus enabling the community to work with you and contribute back.
I'm not interested in filing a minimum of 100 bug reports when you don't have the manpower to process them, I've resolved most of them already (at least the ones related to the php base) and any that I haven't I've noted as "Broken - DNU" so I don't pass anything unstable on to my clients.
Of course, nobody could demand from you to contribute your fixes or your information back - but it is a good citizenship if you do.
-- Stanislav Malyshev, Zend Software Architect [EMAIL PROTECTED] http://www.zend.com/ (408)253-8829 MSN: [EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
