mirror of
https://github.com/ruby/ruby.git
synced 2025-08-15 13:39:04 +02:00
Page:
How To Report
Pages
Assumptions JA
Assumptions
C99 Usage Guidelines
CI Servers
CI用Savings Planの購入
Committer How To JA
Committer How To
Developer How To JA
Developer How To
Developers Meeting
Donation
General Maintenance Policy
Git Migration FAQ JA
Home
How To Backport
How To Contribute
How To Maintain RubyCI Servers
How To Manage Redmine
How To Release JA
How To Report JA
How To Report
How To Request Backport
How To Request Features
Machine Instructions Trace with GDB
Node Position Memo JA
Refinements Spec
Release Engineering 2.1
Release Engineering 2.2
Release Engineering 2.3
Release Engineering 2.4
Release Engineering 2.5
Release Engineering 2.6
Release Engineering 2.7
Release Engineering 3.0
Release Engineering 3.1
Release Engineering 3.2
Release Engineering
Ruby 1.8 Branch Policy JA
Ruby 1.8 Branch Policy
Ruby 1.8 Release Plan JA
Ruby 1.8 Release Plan
Security
Server Resources
Versioning Policy
No results
4
How To Report
Jemma Issroff edited this page 2023-06-06 09:46:03 -04:00
Table of Contents
How to report bugs in Ruby
日本語版(Japanese version): How To Report JA.
If you've encountered a bug in Ruby please report it to the redmine issuetracker available at https://bugs.ruby-lang.org. Do not report security vulnerabilities here, please report through our bounty program page at HackerOne or mail security@ruby-lang.org.
Important
You should contain at least the following items.
- Reproduce process
- your ruby version (
ruby -v
) - reproducible ruby script
- your ruby version (
- Result of reproduce process
- Expected result and the reason why you expect
Steps
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 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.
- Look to see if anyone already reported your issue, try searching on redmine for your problem.
- If you can't find a ticket addressing your issue, create a new one.
- Choose the target version, usually current. Bugs will be first fixed in the current release and then backported.
- 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 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:
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)
Policies
Development
For developers
- Developer How To, Developer How To JA
- How To Contribute
- How To Report, How To Report JA
- How To Request Backport
- How To Request Features
- Developers Meeting
For committers
- Committer How To, Committer How To JA
- Git Migration FAQ JA
- How To Backport
- How To Manage Redmine
- How To Release JA
- How To Maintain RubyCI Servers