Also...
Charles Oliver Nutter wrote:
> > Good bug reports are:
> >
> > 1) reproducible: first time. every time.
> > 2) minimal: nothing that's not needed to reproduce the bug is included.
> > 3) executable: time is our most precious resource.
Are there other criteria that are important to ya'll? Assume 2 bug reports
with equal bug severity. When you're deciding which to work on first, are
there other things you look for that factor into the decision?
One thing that just came to mind is 'scope'. Maybe it's a subtopic under
'minimal'. My current situation is an example. I submitted a Rails sandbox
app that demonstrated the 1206 problem. That 'satisfied' (1) and (3) above.
Given that it's a form-related problem, I'm not sure it could be reduced to
just a jruby snippet. But maybe it could. I do realize now that it would
have been a better submission, done a better job at (2), if I'd taken the
database out of the equation. How else could I have made it better? What
guidance should we give?
Thanks,
Bill
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
