Looking forward to the bug fixing initiative :). I'll help in any area I'm familiar with.
Pádraic Brady http://blog.astrumfutura.com http://www.survivethedeepend.com OpenID Europe Foundation Irish Representative ________________________________ From: Matthew Weier O'Phinney <[email protected]> To: [email protected] Sent: Tuesday, September 1, 2009 5:34:19 PM Subject: Re: [fw-general] How to help solving bugs? -- Jurian Sluiman <[email protected]> wrote (on Tuesday, 01 September 2009, 06:17 PM +0200): > I recently updated from 1.8.x to 1.9.x. Having the idea I had no problem, so I > marked the update as succeeded. Nevertheless I was lately confronted with a > bug > I had seen before. After some digging, I found it. > > > The issue tracker is aware of the bug and I provided a patch when I found the > bug the first time. Still, the issue isn't solved (and it's a really simple > one > to do so) and it's now three months later since I provided the patch (http:// > framework.zend.com/issues/browse/ZF-3726). > > > Not trying to be too specific: there are several issues in the tracker which > are easy to solve. They can still have a big impact on the users of the > framework. How can *we*, the community, help solving these bugs faster? > I know it's a good idea to file issues, create examples and provide patches > when possible. Still, patched issues are not always included in the next > release. Is it a good idea to create a page at the wiki with "easy to fix bugs > with a patch provided", so the ZF developers can scan them quickly? One note: patches are much easier for us to evaluate and apply if they include *unit tests*. Without those, we have to spend as much if not more time evaluating the issue as without the patch - as we have to create and run the test case(s) ourselves. Next note: I'll be announcing an initiative regarding bug fixing within the next week. Stay tuned for details! -- Matthew Weier O'Phinney Project Lead | [email protected] Zend Framework | http://framework.zend.com/
