For bug tracking, JRuby uses JIRA, where you can browse all current bugs and also
see all bugs that have been resolved. We usually try to use JIRA for handling patches too, so go
to the address listed in Appendix C and get an account so you can send in bug reports. When
sending in a report, try to include as much information as possible about your environment
CHAPTER 15 ?– CODA: NEXT STEPS 282
and what you did. If possible, try to narrow down the problem and provide an actual Ruby
script that exhibits it. If we have test cases to look at, it??™s much easier to provide solutions.
When sending in a patch for a bug, you should use the svn diff command to generate
patches. Then, attach them to the bug in JIRA, and also write a small log about what you did to
fix the bug, and what the actual problem in the bug was.
In most cases, patches should provide documentation in the code base. If there are no bugs
for it in JIRA, you can create a new documentation bug, with a subject such as ???RubyKernel
needs more JavaDoc,??? and then send your patches to that bug. Filing everything in JIRA makes
it easy for the developers to keep track of what status everything has and if someone is working
on it. Developers can also keep track of all the versions of patches sent in, and conversations
pertaining to the bug in question.
Home Projects
A large part of contributing to open source projects is working on already existing code. However,
you can also start out by creating something totally new.
Pages:
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417