Bill Walton wrote:
Greetings!
I volunteered to draft a guide to help folks reporting bugs in jruby.
'Draft' is a key word here. By way of introduction... I've got a pretty
extensive background in defining and managing development and test
processes, have been working in Rails since early '06 (right after the
1.0 release), but have absolutely no hands-on background in Java.
As a first stab at content direction....
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.
The Guide will help submitters produce good bug reports by providing
detail on the above, what they mean to the jruby core team, and
instruction to help submitters understand when they're 'done' and have a
bug report that's worthy of submission.
Please consider this just my first attempt at opening a conversation
aimed at learning more about your needs. I'm looking forward to working
with you all on this and, in the process, to learning more about jruby.
This and the resulting conversation would be excellent on the JRuby wiki:
www.headius.com/jrubywiki
It has a little bit of this now, but there's no big flashing sign saying
"HERE'S HOW TO HELP JRUBY" like there ought to be.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
