Writing a Good Bug Report (GBR) is one of the keys to getting the core team to assign a high priority to a bug you may have found. It is key to making a convincing 'argument' that you have, in fact, found a bug. This section is intended to help you help the core team help you.
GBRs have three fundamental characteristics. In short, they are
Writing GBRs is often hard, sometimes frustrating work. Please understand that the core team understands that, and that the contributors who produce GBRs are very much appreciated for helping make JRuby better, that much faster!