Reporting Issues

Reporting security issues

If you’ve found a security vulnerability, please follow these instructions.

Reporting bugs

If you’ve encountered a bug in Ruby, please report it to the Redmine issue tracker available at, by following these steps:

Reporting website issues

If you’re having an issue with the bug tracker or the mailing list, you can contact the webmaster, Hiroshi SHIBATA (

You can report issues with on the repo's issue tracker.

Requesting features

If there’s a new feature that you want to see added to Ruby, you will need to write a proposal on the Redmine issue tracker. When you open the issue, select Feature in the Tracker dropdown.

When writing a proposal, be sure to check for previous discussions on the topic and have a solid use case. You should also consider the potential compatibility issues that this new feature might raise. Consider making your feature into a gem, and if there are enough people who benefit from your feature it could help persuade Ruby core.

Here is a template you can use for a feature proposal:

  Briefly summarize your feature
  Describe current behavior
  Describe your feature in detail
[Use cases]
  Give specific example uses of your feature
  Describe why this feature is necessary and better than using existing features
[See also]
  Link to other related resources (such as implementations in other languages)

Backport requests

If a bug exists in a released version of Ruby, please report this in the issue. Once this bug is fixed, the fix can be backported if deemed necessary. Only Ruby committers can request backporting, and backporting is done by the backport manager. New patch versions are released at the discretion of the backport manager.

Ruby versions can be in one of three maintenance states:

Add context to existing issues

There are several ways you can help with a bug that aren’t directly resolving it. These include: