While updating Xeno to the latest Zend Framework I encountered some regressions. This is typical for software without strictly defined API and unit tests to enforce it, so I was expecting these and found them out with my own Xeno testing.
Being a good community member I reported them promptly to upstream explaining the nature of the issue and giving an example fix, which was working for me. ZF-8767, ZF-8768.
To my excitement when I updated Zend Framework SVN sources checkout an hour later, my fixes was already merged. :-) That’s nice.
But the bugtracker was strangely silent, so I got curious and looked at the SVN log to see whether my solution was correct, how it was implemented finally and commented. There were two commits to the library – first ones for a week or so. But surprisingly none of them mentioned my reported bugs. One fix was merged as a [GENERIC] bugfix, and second was expanded to a fix for the same error class in many instances and mentioned some other bug.
The real surprise came an hour later from the bugtracker. My reports were closed by the person committing changes to the SVN as… “Not reproducible within trunk. Probably already fixed.” WTF? What nerve.
Dojo Toolkit community was very skeptic when Zend offered joint-effort proposal. One might see why.
For me this is a complete credibility lost for Zend Framework. I doubt I will use it in any other project. You may think twice before doing so too.
What’s cheaper paying someone to code or having a “community”?