Carl Witty wrote: > On Wed, Mar 11, 2009 at 11:39 PM, Stefan Behnel <[email protected]> wrote: >> 2) Every trac ticket must have a bug test case associated with it. This >> means that there must be a failing test case in tests/bugs/ named >> "nicely_descriptive_name_here_Txyz.pyx" (where 'xyz' is the ticket number), >> or a patch in trac that adds this test case. See >> >> http://wiki.cython.org/HackerGuide >> >> Please try to do this even for the tricky cases that feel like there isn't >> a good test case. Reproducing a bug is critical for fixing it, and having a >> test case is critical for not breaking it in the future. > > Does that mean I can't report bugs to trac anymore, without > constructing a test case in the form of a Cython patch? If so, then > -0. (I probably just wouldn't bother reporting bugs any more under > such a rule.)
No, reporting bugs is open to everyone. The above doesn't mean the reporter of a bug *must* be the one to provide the test case. I just wanted to stress the fact that we need a test case that must go in before the fix, and that a test case makes it easier for us to reproduce and fix the bug. So there is a reason to prioritise tickets that contain a test case, as tickets without a test case are more work. I'll clarify that on a Wiki page later today. Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
