HowtoReport » History » Version 3

« Previous - Version 3/5 (diff) - Next » - Current version
Zachary Scott, 12/23/2013 06:47 AM


=begin
= HowtoReport

How to report bugs in Ruby

日本語版(Japanese version): HowToReportJa.

If you've encountered a bug in Ruby please report it to the redmine issue
tracker available at {bugs.ruby-lang.org}[[http://bugs.ruby-lang.org/]]. Do not
report security vulnerabilities here, please mail security@ruby-lang.org.

There are a few simple steps you should follow in order to receive feedback
on your ticket.

  • If you haven't already, {sign up for an account}[[https://bugs.ruby-lang.org/account/register]] on the bug tracker.
  • Try the latest version.

    If you aren't already using the latest version, try installing a newer
    stable release. See
    {Downloading Ruby}[[http://www.ruby-lang.org/en/downloads/]].

  • Look to see if anyone already reported your issue, try
    {searching on redmine}[[https://bugs.ruby-lang.org/projects/ruby-trunk/issues]]
    for your problem.

  • If you can't find a ticket addressing your issue,
    {create a new one}[[https://bugs.ruby-lang.org/projects/ruby-trunk/issues/new]].

  • Choose the target version, usually current. Bugs will be first fixed in the
    current release and then {backported}[rdoc-label:label-Backport+Requests].

  • Fill in the Ruby version you're using when experiencing this issue
    (ruby -v).

  • Attach any logs or reproducible programs to provide additional information.
    Reproducible scripts should be as small as possible.

  • Briefly describe your problem. A 2-3 sentence description will help give a
    quick response.

  • Pick a category, such as core for common problems, or lib for a standard
    library.

  • Check the {Maintainers
    list}[[https://bugs.ruby-lang.org/projects/ruby/wiki/Maintainers]] and assign
    the ticket if there is an active maintainer for the library or feature.

  • If the ticket doesn't have any replies after 10 days, you can send a
    reminder.

  • Please reply to feedback requests. If a bug report doesn't get any feedback,
    it'll eventually get rejected.

=== Reporting to downstream distributions

You can reports downstream issues for the following distributions via their bugtracker:

  • {debian}[[http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ruby-defaults]]
  • {freebsd}[[http://www.freebsd.org/cgi/query-pr-summary.cgi?text=ruby]]
  • {redhat}[[https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=MODIFIED]]
  • {macports}[[http://trac.macports.org/query?status=assigned&status=new&status=reopened&port=~ruby]]
  • etc (add your distribution bug tracker here)

=== Platform Maintainers

For platform specific bugs in Ruby, you can assign your ticket the current
maintainer for a specific platform.

The current active platform maintainers are as follows:

[mswin32, mswin64 (Microsoft Windows)]
NAKAMURA Usaku (usa)
[mingw32 (Minimalist GNU for Windows)]
Nobuyoshi Nakada (nobu)
[IA-64 (Debian GNU/Linux)]
TAKANO Mitsuhiro (takano32)
[Symbian OS]
Alexander Zavorine (azov)
[AIX]
Yutaka Kanemoto (kanemoto)
[FreeBSD]
Akinori MUSHA (knu)
[Solaris]
Naohisa Goto (ngoto)
[RHEL, CentOS]
KOSAKI Motohiro kosaki
[Mac OS X]
Kenta Murata (mrkn)
[cygwin, bcc32, djgpp, wince, ...]
none. (Maintainer WANTED)

=end