U:RDoc::TopLevel[ i I"bug_triaging.rdoc:EFcRDoc::Parser::Simpleo:RDoc::Markup::Document: @parts[(S:RDoc::Markup::Heading:
leveli: textI"Bug Triaging Guide;To: RDoc::Markup::BlankLine o: RDoc::Markup::Paragraph;[I"RThis guide discusses recommendations for triaging bugs in Ruby's bug tracker.;T@
S; ;
i; I"$Bugs with Reproducible Examples;T@
o;
;[ I"RThese are the best bug reports. First, consider whether the bug reported is ;TI"Sactually an issue or if it is expected Ruby behavior. If it is expected Ruby ;TI"Obehavior, update the issue with why the behavior is expected, and set the ;TI"status to Rejected.;T@
o;
;[ I"SIf the bug reported appears to be an actual bug, try reproducing the bug with ;TI"Rthe master branch. If you are not able to reproduce the issue on the master ;TI"Qbranch, try reproducing it on the latest version for the branch the bug was ;TI"Lreported on. If you cannot reproduce the issue in either case, update ;TI"Pthe issue stating you cannot reproduce the issue, ask the reporter if they ;TI"Ocan reproduce the issue with either the master branch or a later release, ;TI"$and set the status to Feedback.;T@
o;
;[
I"PIf you can reproduce the example with the master branch, try to figure out ;TI"Kwhat is causing the issue. If you feel comfortable, try working on a ;TI"Qpatch for the issue, update the issue, and attach the patch. Try to figure ;TI"Nout which committer should be assigned to the issue, and set them as the ;TI".assignee, and set the status to Assigned.;T@
o;
;[ I"SIf you cannot reproduce the example with the master branch, but can reproduce ;TI"Sthe issue on the latest version for the branch, then it is likely the bug has ;TI"Oalready been fixed, but it has not been backported yet. Try to determine ;TI"Pwhich commit fixed it, and update the issue noting that the issue has been ;TI"Kfixed but not yet backported. If the Ruby version is in the security ;TI"Qmaintenance phase or no longer supported, change the status to Closed. This ;TI"Qchange can be made without adding a note to avoid spamming the mailing list.;T@
o;
;[I"TFor issues that may require backwards incompatible changes or may benefit from ;TI"Ogeneral committer attention or discussion, consider adding them as agenda ;TI"Titems for the next committer meeting (https://bugs.ruby-lang.org/issues/14770).;T@
S; ;
i; I"#Crash Bugs Without Reproducers;T@
o;
;[I"SMany bugs reported have little more than a crash report, often with no way to ;TI"Sreproduce the issue. These bugs are difficult to triage as they often do not ;TI" contain enough information.;T@
o;
;[
I"OFor these bugs, if the Ruby version is the master branch or is the latest ;TI"Srelease for the branch and the branch is in normal maintenance phase, look at ;TI"Qthe backtrace and see if you can determine what could be causing the issue. ;TI"SIf you can guess what could be causing the issue, see if you can put together ;TI"Qa reproducible example (this is in general quite difficult). If you cannot ;TI"Rguess what could be causing the issue, or cannot put together a reproducible ;TI"Rexample yourself, please ask the reporter to provide a reproducible example, ;TI"'and change the status to Feedback.;T@
o;
;[ I"RIf the Ruby version is no longer current (e.g. 2.5.0 when the latest version ;TI"Son the Ruby 2.5 branch is 2.5.5), add a note to the issue asking the reporter ;TI"Sto try the latest Ruby version for the branch and report back, and change the ;TI"Sstatus to Feedback. If the Ruby version is in the security maintenance phase ;TI"Ror no longer supported, change the status to Closed. This change can be made ;TI"without adding a note.;T@
S; ;
i; I"+Crash Bugs With 3rd Party C Extensions;T@
o;
;[I"SIf the crash happens inside a 3rd party C extension, try to figure out inside ;TI"Mwhich C extension it happens, and add a note to the issue to report the ;TI"Jissue to that C extension, and set the status to Third Party's Issue.;T@
S; ;
i; I"Non-Bug reports;T@
o;
;[I"PAny issues in the bug tracker that are not reports of problems should have ;TI"Qthe tracker changed from Bug to either Feature (new features or performance ;TI"Jimprovements) or Misc. This change can be made without adding a note.;T@
S; ;
i; I"Stale Issues;T@
o;
;[ I"TThere are many issues that are stale, with no updates in months or even years. ;TI"SFor stale issues in Feedback state, where the feedback has not been received, ;TI"Ryou can change the status to Closed without adding a note. For stale issues ;TI"Uin Assigned state, you can reach out to the assignee and see if they can update ;TI"Othe issue. If the assignee is no longer an active committer, remove them ;TI"3as the assignee and change the status to Open.;T:
@file@:0@omit_headings_from_table_of_contents_below0